- Product: 360 Core Client Center
How does Athens and Shibboleth user authentication work with 360 discovery services?
Our 360 discovery services all support user authentication using Shibboleth and Athens. Support for Athens and Shibboleth makes it easier for users (patrons) to access the full breadth of your library's discovery and access services, whether the patron is a remote or local user.
360 Search began supporting Athens and Shibboleth for user authentication in the summer of 2008. 360 Link and E-Journal Portal support came in July 2009.
The user authentication service is a single-sign-on (SSO) solution into all our 360 discovery services, but that does not mean it is an SSO solution into Athens- or Shibboleth-enabled content providers.
When a service is set up as an Athens or Shibboleth-protected service, your library can prompt a patron to enter their SSO login information in order to use that service. Once the patron has logged into Athens or Shibboleth, they can see results with that service. Support for an SSO solution across content providers requires the inclusion of a third-party proxy/URL-rewriting service.
ProQuest is a member of several federations, and we are in the process of joining more:
|Netherlands SURF federatie||Active -- Click here for details.|
|Japan GakuNin||Active (update April 1)|
|Australian Access Federation||We need several interested customers; contact your Sales Representative if interested.|
To enable Athens or Shibboleth for your ProQuest services, go to the Client Center's Administration Console and select the User Authentication tab.
You can also read Serials Solutions' Participant Operational Practices (POP) document for Shibboleth.
- Date Created: 9-Feb-2014
- Last Edited Date: 20-Feb-2014
- Old Article Number: 7480