View by category
Which SAML attributes does Elsevier SP require?
Last updated on May 07, 2026
For a comprehensive IdP configuration FAQ please visit How do I set up federated access as a librarian or administrator?
Elsevier’s SP manages SAML-based authentication for a wide range of products and services, each with different identity and access requirements.
These include:
- Products accessible anonymously, with optional personalization (e.g. ScienceDirect, Scopus)
- Products requiring user-level personalization (e.g. SciVal, Mendeley)
- Access via institutional subscriptions, free services, hybrid models, or invitation-based access
To support this variety while keeping IdP configurations manageable, we define a minimum set of required attributes that ensures both access control and a consistent user experience.
An IdP must release one type of pseudonymous attribute.
We support the following attributes (in order of preference):
- pairwiseID (defined in the OASIS specification)
- subjectID (the same OASIS document)
If already in use, the following legacy attributes are still supported:
- eduPersonTargetedID (deprecated)
- persistent NameID (deprecated; must be opaque, non-reassignable, case-sensitive)
A pseudonymous identifier allows Elsevier to:
- Link institutional access to user accounts (when needed)
- Support personalization features across products
- Detect and manage misuse at the individual user level (SIRTFI compliance)
Without it, access may still work, but functionality and operational control are limited.
Note: The attribute values do not need to be known to Elsevier in advance.
New IdP setup
- Preferably release pairwiseID
Existing IdP (not yet using pairwiseID)
- Add pairwiseID alongside your current identifier
- Keep both for a transition period (recommended: 1–2 months)
- Afterward, the old attribute can be removed
This ensures existing users remain recognized and retain their settings.
If you switch identifiers without overlap, returning users will not be recognized and may need to relink their accounts manually:
How can I link my new to my old institutional/SSO credentials?
Mismatch between eduGAIN and local federation metadata
We are aligning metadata across federations.
The metadata published in eduGAIN takes precedence.
Why multiple pseudonymous attributes appear in metadata
SP metadata may list multiple supported attributes.
This indicates compatibility, only one needs to be released by the IdP.
An IdP may release one of the two supported group attributes.
Any entitlement or affiliation values must be shared with Elsevier support to be configured, otherwise they will be ignored.
Both attributes are multivalue.
We evaluate the full attribute value.
Supported attribute names:
urn:oid:1.3.6.1.4.1.5923.1.1.1.7urn:mace:dir:attribute-def:eduPersonEntitlement
Default value:
urn:mace:dir:entitlement:common-lib-terms
Users without a valid entitlement value will not receive access to subscription content.
Alternative values can be configured in coordination with Elsevier support.
If ePE cannot be released, please contact support to discuss alternatives. This requires that institutional credentials are not issued to non-entitled users (e.g. alumni, affiliates, walk-in users).
eduPersonScopedAffiliation (ePSA)
Supported attribute names:
urn:oid:1.3.6.1.4.1.5923.1.1.1.9urn:mace:dir:attribute-def:eduPersonScopedAffiliation
Required for shared IdPs so we can distinguish between organizations.
Did we answer your question?
Related answers
Recently viewed answers
Functionality disabled due to your cookie preferences