EZproxy-Alma User Data Integration version 1
Ian Chan (Unlicensed)
Lauren Magnuson (Unlicensed)
Owned by Ian Chan (Unlicensed)
| Target release | version 1 |
|---|---|
| Epic | |
| Document status | DRAFT |
| Document owner | |
| Project Team | Elizabeth Altman (Unlicensed), G (Unlicensed), Lauren Magnuson (Unlicensed), Renaldo Gjoshe (Unlicensed) |
| Developers | Lauren Magnuson (Unlicensed) |
| QA |
Completed Project
https://github.com/CSU-ULMS/EZProxy-Alma-Authentication
Goals
- Utilize Alma data to ensure e-resource is restricted to users who have active accounts in Alma.
Background and strategic fit
E-resource license agreements limit usage to users who have active accounts in Alma. LDAP authentication for some campuses does not accurately reflect student enrollment status.
Assumptions
- EZproxy is already deployed.
- User accounts in Alma provide updated account expiration dates.
Requirements
| # | Title | User Story | Importance | Notes |
|---|---|---|---|---|
| 1 | Alma verification of user account status | At login, EZproxy checks Alma via user data API to ascertain whether user account is active. | Must Have | Completed |
| 2 | Alma verification of user group | At login, EZproxy checks Alma user group to ensure user group is authorized remote access | Must Have | Completed |
| 3 | Check LDAP for Authentication | At login, username and password are checked to authenticated user | Must Have | Completed |
Not Doing
- User Interface for Login page - up to each individual campus to customize according to needs
Major Tasks
Description / Lead / Completion
- share current CSUN code for this integration in repo on Bitbucket.org / Lauren Magnuson (Unlicensed) /
- Create requirements list for the end product / Lauren Magnuson (Unlicensed) /
- Map out steps in EZproxy authentication / Elizabeth Altman (Unlicensed) /
- Survey to campuses asking for contact and specific use case details / Lauren Magnuson (Unlicensed) /