Overall Status
Status | ||||
---|---|---|---|---|
|
Major Milestones
Stage | Complete By | Status | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Meet with Chancellor's Office Identity Management Group and vanguard campuses (Fresno, Fullerton, Northridge) to discuss project. |
|
| ||||||||
Meet with Ex Libris to discuss options for Shibboleth. |
|
| ||||||||
All campus Primo SPs registered with InCommon |
|
| ||||||||
Initial testing of Shibboleth with Chancellor's Office. |
|
| ||||||||
Introduce campus Identity Management groups to project |
|
| ||||||||
Campus Primo instances made available |
|
| ||||||||
Project Team
Role | Name |
---|---|
Project lead | |
Chancellor's Office Contacts | Marcus Mizushima (Shibboleth) Michael Trullinger (Dir. Tech Infr.) Carol Kiliany (Project Manager) |
Ex Libris Contacts | Dolph Chaney (Project Manager) James Tapia (Shibboleth) |
Informed / Other Stakeholders |
Why are we doing this?
Staff need to be able to login to Alma and end-users need to be able to login to Primo to perform tasks. Using Shibboleth as the authentication source Adopting a systemwide approach allows us to streamline the process for setting-up authentication and . It also allows us to coordinate this task work with the related task of automating the loading of patron data from PeopleSoft to Alma.
Scope
Requirements / Risks
ResourcesDocumentation
Meeting Notes: