[DRAFT] [DRAFT] [DRAFT] [DRAFT]
Is this document for ME?
It is if you are a staff member at an academic institution (that uses EZProxy) who wishes to begin implementing Shibboleth access to library resources, but are unsure about what is required and what is involved.
Why this document?
By laying out the necessary pre-requisites as well as the steps involved, the hope is that this document will enable the reader to decide IF moving to Shibbolized access to library resources is feasible at his/her institution, and if it is, will provide a "cookbook" for the process.
What are the pre-requisites for integrating Shibboleth and EZproxy?
- An institution-wide (enterprise) directory service that contains information about the users for whom you wish to authorize access to electronic resources.
- An Identity management environment (policies and business practices) that governs the management of identity information for the users in the enterprise directory. This is necessary to build and maintain the trust necessary to participate in a federation such as InCommon.
- A Shibboleth IdP from which service providers (EZproxy itself, JSTOR, OCLC, Elsevier, etc) can obtain sufficient identity information about each user of their services who requests access.
- An EZproxy installation that provides authenticated remote access to library resources.
- Institutional membership in a federation such as InCommon