View by category
Which RE (SAML) Federations does Elsevier support?
Last updated on July 29, 2025Elsevier SP consumes the metadata of some federations through eduGAIN and some directly from their own feeds. Our metadata is also available in some federations directly and some get it via eduGAIN. That means that our SP signals slightly different attribute requirements to different IdPs. That's all for legacy reasons and not intentional behaviour.
We're working on gradually aligning these requirements in early 2025 into a simple set:
- must release one pseudonymousID
- should release entitlement attribute
- may release affiliation attribute
If your federation is listed in the table below then customer support can easily enable SAML-based federated access for you; all information you may need is available here.
eduPersonEntitlement can be released as one of the two versions:
name="urn:oid:1.3.6.1.4.1.5923.1.1.1.7"
name="urn:mace:dir:attribute-def:eduPersonEntitlement"
The default value is: urn:mace:dir:entitlement:common-lib-terms but you may negotiate different values with Elsevier customer support.
For some federation members releasing ePE is mandatory, for other optional. We’re working towards making it mandatory for all IdPs.
eduPersonScopedAffiliation can be released as one of the two versions:
name="urn:oid:1.3.6.1.4.1.5923.1.1.1.9"
name="urn:mace:dir:attribute-def:eduPersonScopedAffiliation"
This attribute is optional, unless your IdP is shared by multiple organizations.
The values have to be shared with Elsevier customer support in advance.
Did we answer your question?
Related answers
How do I set up federated access as a librarian or administrator?
I'm a librarian or administrator and my users are having trouble signing in via federated access
How does federated access work?
How can I build a WAYFless URL to Elsevier products?
What should I do if I can't sign in via my institution, Shibboleth or OpenAthens?
Recently viewed answers
Functionality disabled due to your cookie preferences