| Table of Contents |
|---|
Introduction
Hybrid Authentication is an operational scenarios many libraries are currently involved in: online publishers resources can be accessed both via IP based authentication and through a Web Single-Sign-On Session. AARC aims at promoting the adoption of federated credentials in accessing services; This pilot shows how Libraries can effectively use the OCLC EZproxy tool (which they often already have available, acting as an IP proxy) by levering its Acces Mode Switch feature, once configured accordingly. EZproxy can this act as a switch from IP based proxy to access non federated resources to SAML SSO redirect proxy, to entitle users to federated online resources if they own SAML2-IDP provided credentials.
This feature is of great potential in pushing libraries towards the adoption of federated identities and the provisioning of federated credentials to their users: EZproxy is a very popular tool widely adopted by Libraries worldwide, so the goal of this pilot is to show that, after proper configuration, it enables libraries to provide services to their users via Identity Federations and SAML IDPs.
Detailed description
A detailed description of the aim and approach of this pilot and how it maps to the AARC Blueprint Architecture is available here
Demonstration Portal
Workflow
For federated users
| 1. | Access EZ proxy demo instance at https://ezproxy.fi.infn.it/ |  |
| 2. | Login to EZproxy portal with your federated ID:
|  |
| 3. | Choose the Federated Resource Dogs 101 (redirection to SSO) (note the URL http |
This sections gathers all required information to try out and hands on experience on the pilots provided by AARC SA1
Demo video
https://drive.google.com/open?id=0B6nLU4k7ZZvfUjNhNHdKYkNHTmc
Transcript https://drive.google.com/open?id=0B6nLU4k7ZZvfU3lNalN2Q2JsYzA
Scenario A] FEDERATED USER
a USER, provided with FEDERATED ID,
firstly logs in the institution EZproxy and, if succesfully authenticated, gets 1. a SSO session and 2. a shielded access masked with the IP addreess of the proxy.
When she accesses
-> A.1] a FEDERATED RESOURCE, by means of SAML SSO session, she gets access to the resource with SAML authentication;
-> A.2] a NOT FEDERATED RESOURCE restricted to authorised IPs, by means of REWRITING properties of the proxy she gets access to the resource because she's authorized having the IP address of the proxy.
The USER: you with your federated credential
...
...
...
|
...
...
|  |
| 4. | Choose the Not Federated Resource Cats 101 (via proxy) (note the URL http://ezproxy.fi.infn.it/login?url= |
...
...
|
...
|
...
|
...
...
|  |
Scenario B] NOT FEDERATED USER
in this case the user is not provided with Federated access and is permitted via her IP address.
The USER: you with EZproxy local credential (in this way you get the authorised IP address)
For non-federated users
...
| 1. | Access EZ proxy demo instance at |
...
| ||
| 2. | Login to EZproxy portal as a library walk-in guest:
|  |
| 3. | Choose the Federated Resource Dogs 101 (redirection to SSO) (note the URL http://ezproxy.fi.infn.it/login?url= |
The federated resource is: https://sp24-test.garr.it/i...
...
...
|
...
| |
| 4. | Choose the Not Federated Resource Cats 101 (via proxy) (note the URL http:// |
...
...
...
|
...
|
...
| |
Components
Benefits
Demo Video
https://drive.google.com/open?id=0B6nLU4k7ZZvfaUM4OTJtTmlFN28
Transcript https://drive.google.com/open?id=0B6nLU4k7ZZvfcGNybTFXZ0VaRlk
Benefts
- A user use only one unified method of authentication to access both federated and not federated resources
- For each resource the Library logs the access in a unified way. If a Resource is federated, only federated access will be allowed, and IP based auth wont be permitted anymore. If a Resource is not federated, the user gets the access via IP address auth, and the proxy will log the access o that resource in this way.
...