View by category
How do I set up a proxy server to access subscribed products?
Last updated on February 14, 2025Many of our customers use proxy servers to manage access to their subscribed services for remote users.
There are many different proxy products in use with varied and diverse capabilities and complex configuration requirements. For this reason, we are unable to formally provide support for proxy servers and cannot guarantee that they will work. Any proxy-related access issues should be directed to the proxy vendors' support teams. We aim to provide advice to help with debugging on a best-effort basis.
If your institution uses a proxy service, please send its proxy IP address to your Elsevier customer service. This will then be configured for access to your subscribed products.
IP addresses can only be configured if they are registered to your institution and for your exclusive use. Shared IPs cannot be configured.
Elsevier has introduced a new access management system in order to improve the single sign on experience across our products and ensure a consistent experience when registering and signing in with an Elsevier account. We are gradually migrating our products to the new mechanism: many products already use it, others will migrate to it in the future.
In general, there is no action required from Elsevier customers with regards to the new authentication mechanism, however if you are using a proxy, please ensure that the id.elsevier.com domain is known to it. Configuration is proxy-specific: some proxies may need to whitelist this domain, whilst others may need to rewrite it in order to allow the user to continue the session.
If you are using OCLC's EZProxy product, you must configure your proxy with the up-to-date version of the stanza which is published at ScienceDirect and Scopus or Engineering Village pages.
Please be sure to include the complete stanza as given, including the section specifically relevant to the id.elsevier.com domain:
Title -hide Elsevier Identity
URL https://id.elsevier.com
HJ https://id.elsevier.com
HJ id.elsevier.com
DJ id.elsevier.com
Find redirect_uri=https://
Replace redirect_uri=https://^A
If you are using III WAM you will need to add the domains you encounter at Elsevier to your WAM forward table.
To access any Elsevier product, such as ScienceDirect, you must add:
id.elsevier.com
For ScienceDirect specifically, please also add:
sciencedirect.com
sciencedirectassets.com
reader.elsevier.com
linkinghub.elsevier.com
sd-cart.elsevier.com
To access Mendeley, please add:
mendeley.com
If you're using AdminTool, add the following domains to your forward table:
admintool.elsevier.com
online.tableau.com
help-admintool.elsevier.com
tableau-admintool.elsevier.com
If you are using MuseKnowledge Proxy, you have to make sure that the latest version of the Source Profiles are in place for your MuseKnowledge Proxy Applications, as published here:
https://www.edulib.com/muse-proxy/sources/profiles/ScienceDirect.xml
https://www.edulib.com/muse-proxy/sources/profiles/Scopus_IP.xml
The Source Profile is an XML file containing all the necessary rules for rewriting a certain publisher platform.
Did we answer your question?
Related answers
Set up remote access for your users
Which RE (SAML) Federations does Elsevier support?
How do I set up federated access as a librarian or administrator?
Which access methods does Elsevier support?
I'm a librarian or administrator and my users are having trouble signing in via federated access
Recently viewed answers
Functionality disabled due to your cookie preferences