What are the supported authentication methods for HeinOnline access?
These are the supported forms of HeinOnline authentication:
The institution’s account administrator is given a single username/password which can be distributed to all authorized users at his/her discretion. Users enter the credentials on https://heinonline.org/HOL/Welcome
2. IP address authentication
Institution provides their static, public-facing IP addresses to firstname.lastname@example.org. The addresses are whitelisted and any user accessing HeinOnline from a whitelisted IP address is granted access to the database without being prompted for a username/password.
3. Proxy Server
Same as IP authentication, but the institution provides the IP address of their proxy server. The institution needs to account for heinonline.org in their proxy configuration. EZProxy customers should refer to https://help.oclc.org/Library_Management/EZproxy/Database_stanzas/HeinOnline. Users should access HeinOnline from a url that contains the institution’s proxy prefix.
4. Referring URL
The organization puts a link to HeinOnline on a password-protected page that can only be accessed by authorized users. HeinOnline whitelists the URL, allowing any user who clicks on the HeinOnline link access to the database without being prompted for a username/password
5. Federated Access/SAML/SSO/Shibboleth/OpenAthens
HeinOnline uses OpenAthens Keystone as our federated access management solution. In addition to supporting access for OpenAthens members, we also support many Shibboleth Federations, including:
If your institution’s metadata is published with any of the federations listed above, we should be able to set up federated access. Contact email@example.com and provide your organization’s entity ID to get started.
We have also had success implementing SAML authentication for organizations using the following products:
If you utilize any of the products listed above and would like to explore the possibility of using it for HeinOnline access, please inquire with firstname.lastname@example.org.