| Navigation Map |
|---|
| phase |
|---|
| phase |
|---|
| cellWidth | 200 |
|---|
| cellHeight | 40 |
|---|
|
Phase I Use Cases and Technology Recommendations What: Libraries face special situations in making online resources available. Some resources, such as the catalog, may be open to all who enter the building. For other Other resources, such as specialized databases, the library may have a vendor contract that restricts access may be open to anyone physically in the library, as well as to those with university credentials (faculty, staff and students)regardless of their physical location. Add to this the desire for campus-wide single sign-on, remote access for those with university credentials, and providing a positive experience for walk-in public users; and the situation becomes complex. Who: Several libraries formed the InCommon-Library collaboration to explore solutions to these various issues. After exploring various potential solutions, InC-Library settled on . The consensus was a hybrid technology, using EZProxy (for remote user authentication) and Shibboleth for single sign-on convenience and federated access to external resources. EZProxy can use Shibboleth for initial user authentication, providing a single login for both remote access and campus resources, as well as a seamless user experience when transitioning individual resource access from IP to Shibboleth.
See the Phase I 1 page for use cases and presentations and other information. Phase I included six institutions: Cornell University, Penn State, UC-San Diego, The University of Chicago, University of Maryland, and the University of Washington. II You can help the InC-Library collaboration take the next step and implement the EZProxy/Shibboleth hybrid technology. This will be a collaborative effort among several schools to use the hybrid solution in providing access to protected library resources, as appropriate, to campus-based users, walk-up users, and remote users with campus credentials. We are looking for colleges and universities interested in implementing this solution -- and working with others in making it better. To participate, contact Steven Carmody (Steven_Carmody AT brown DOT edu). |