View by category
Which access methods does Elsevier support?
Last updated on February 11, 2025Not all customers have the same authentication infrastructure, and some may not have any at all. To accommodate this variety, Elsevier supports multiple authentication methods, ensuring all users can access their subscriptions regardless of their organization’s capabilities. Although the ideal scenario would involve universal federated access using SAML 2.0, real-world complexities necessitate a range of solutions.
This article outlines the different authentication methods Elsevier supports, ranked by preference, and provides a guide for their setup and benefits.
Order of Authentication Methods
- Overview: This is the preferred authentication method for organizations with robust infrastructure. Federated access based on SAML 2.0 enables seamless single sign-on (SSO), allowing users to access Elsevier products through their organization’s identity provider.
- Benefits:
- Single sign-on for multiple resources.
- Secure and widely adopted.
- Reduces the need for multiple logins.
- Recommended For: Institutions with an Identity Provider (IdP) that supports SAML 2.0, enabling users to access resources with their institutional credentials.
- How It Works: A user visits a product, clicks 'Check Access' or 'Sign In,' selects their institution, and signs in via the library's Identity Provider (IdP). The user is then redirected to the product, gaining access to institutional subscriptions. Libraries can also provide WAYFless URLs to bypass some navigation steps, leading users directly to the authenticated product.
- How does it get set up?: The library provides Elsevier with their entityID, which is configured for access to the library’s subscriptions. Changes to the entityID must be communicated to Elsevier.
- Must haves: The institution must have an Authentication and Authorization Infrastructure (AAI) supporting SAML 2.0 and be a member of a federation that Elsevier supports.
- User personalization: Users can create a personal account linked to institutional credentials if the IdP releases a persistent ID. Personalization may be optional or mandatory, depending on the product.
- Usage reporting: Usage reporting varies by product. Some products allow department-level reporting based on group attributes released by the IdP.
- Drawbacks: Users need to learn how to access their institution's login page for product visits, adding complexity, especially for those expecting a direct login. This extra step can cause confusion or frustration, particularly for first-time or infrequent users.
- Overview: Email domain confirmation is an alternative for organizations that do not support federated access. This method verifies access based on the user’s email domain, ensuring that users from recognized organizations can log in.
- Benefits:
- Simple to implement.
- Suitable for organizations that lack federated SSO.
- Recommended For: Organizations without a sophisticated authentication system.
- How It Works: A user signs in with their institutional email. The first time they log in, Elsevier sends a confirmation email to verify the mailbox. Once confirmed, they can access institutional subscriptions from anywhere. Periodic re-verification is required every six months.
- How does it get set up?: The library provides Elsevier with its institutional domains, which are configured for subscription access. Any changes to domains must be reported to Elsevier.
- Must haves: The institution must own the domain(s), and users must have their own institutional mailbox.
- User personalization: Personalization is mandatory, as users must register to verify institutional affiliation. The account can be linked to their institution after email verification.
- Usage reporting: Libraries can report usage per department if they specify which domains belong to each department.
- Drawbacks: Organizations that change their email domain (e.g., due to mergers or rebranding) may face additional hurdles in updating their status with Elsevier, potentially interrupting access for users.
- Related Links
- Overview: IP-based authentication automatically grants access to users who are within the institution’s recognized IP address range. Users within a registered IP range are automatically granted access without needing to log in.
- Benefits:
- Seamless, automatic access for users within an authorized network.
- Works well for large organizations with stable IP infrastructure.
- Recommended For: Organizations with well-defined and static IP ranges.
- How It Works: A user gains automatic access to institutional subscriptions by visiting a product from within the institution’s network.
- How does it get set up?: The library provides Elsevier with its IP address range, which is configured for access. IP range changes must be communicated to Elsevier.
- Must haves: The library must have exclusive IPv4 address ranges and prove ownership.
- User personalization: Users can create personal accounts, but access to institutional subscriptions is limited to within the IP range
- Usage reporting: Libraries can report usage per department based on IP ranges assigned to each department.
- Drawbacks: Access is tied to the institution's network. Blocking due to abuse affects all users on the same IP.
- Overview: Proxy/VPN authentication grants users access to subscriptions when they connect through a specific proxy or VPN link.
- Benefits:
- Simple IP setup for access.
- One IP address for setup and maintenance.
- Recommended For: Institutions that rely on proxies or VPNs for remote access.
- How It Works: Users gain access to institutional subscriptions via a proxy link. Without using the proxy, access is not granted.
- How does it get set up?: The library provides Elsevier with its proxy IP address. Any changes must be communicated to Elsevier.
- Must haves: A functional proxy service or VPN is required, with unique IP addresses for the institution.
- User personalization: Personal accounts can be created, but access is only available through the proxy.
- Usage reporting: Usage reporting is available for the entire institution based on proxy IP. Department-level reporting is not supported.
- Drawbacks: Users must always use proxy links for access. Proxy configuration can be complex.
- Related links:
- Overview: A Registration ID is issued to users to facilitate access to Elsevier products. It serves as an access credential for users who may not be part of a federated authentication system or cannot use email domain confirmation.
- Benefits:
- Useful for individuals or smaller organizations.
- Allows for controlled access without relying on institutional systems.
- Recommended For: Users who cannot authenticate via institutional or IP-based methods.
- How It Works: A user redeems a Reg ID provided by the library to access institutional subscriptions. After redemption, access is available from anywhere.
- How does it get set up?: Libraries generate Reg IDs via Elsevier’s Admin Tool and distribute them to users.
- Must haves: Libraries interact with users directly. Elsevier does not issue Reg IDs.
- User personalization: Reg ID activation requires account registration. Existing accounts can be linked to the institution.
- Usage reporting: Libraries can report usage per department based on Reg ID distribution.
- Drawbacks: Requires manual administration by the library.
- More information: Elsevier Admin Tool for librarians
- Overview: Guest access allows users to access free content and features on Elsevier products without institutional subscriptions.
- Benefits:
- Users can access free content and features without institutional subscriptions.
- Simplifies access for unaffiliated users.
- Recommended For: Users seeking free content and features on Elsevier platforms.
- How It Works: Users can access free content or features of Elsevier products without institutional subscriptions. Personal accounts can be created for personalization features.
- How does it get set up?: No setup required for guest access to free content.
- Must haves: No setup is required for guest access to free content.
- User personalization: Personal accounts can be created for personalization features, even without institutional access.
- Usage reporting: Not applicable.
- Drawbacks: No access to subscription content.
- Overview: This option enables us to display a customized message giving users instructions on how to obtain remote access via their institution. It can be used, for example, to include a link to the institutions proxy server portal or provide instructions for signing in via VPN.
- How It Works: Institutions supply Elsevier with the message content, which can include instructions or links to proxy servers or VPNs. This message is displayed to users trying to gain access.
For further information or support with any of these methods, please contact Elsevier customer support or refer to the appropriate Elsevier tools.
Did we answer your question?
Related answers
Set up remote access for your users
How do I set up federated access as a librarian or administrator?
Which RE (SAML) Federations does Elsevier support?
How do I set up a proxy server to access subscribed products?
Recently viewed answers
Functionality disabled due to your cookie preferences