SSO / PeopleSoft Discussion (w/CO)
- CO Identity Group (works with identity management at all campuses) can make a mandate about the use of Shibboleth
- Can work with Identity Group to ensure campuses provide consistent configuration for Shibboleth in Primo
- For some campuses (i.e., San Diego) can work with them to attempt to unify directories for easier implementation of Shibboleth
- Needs to see Ex Libris documentation regarding Shibboleth implementation (David Walker will provide )
- Would also like to get in touch with key people at San Marcos
- PeopleSoft Patron Load Extract Automation
- Need more information about the parameters of what this looks like / what data is needed
- Should we create a recommended list of basic fields?
- Concerns about Shibbolizing other library campus services (e.g., ILLiad / EZProxy)
- Many campus directories lack attributes indicating which users are 'Active' Users. For example, many entries in campus directories remain essentially active indefinitely. Libraries have contracts that often require that only current students, faculty, and staff are able to access library systems.
- CO Identity Group can encourage campuses to add attributes indicating user type (student, faculty staff) and who is and who is not active
- PeopleSoft Financials Integration
- Need to know the parameters of what is needed in PeopleSoft for financials integration (i.e., invoices?)