Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Legend:
Status
titlenot started
Status
colourYellow
titleIN PROGRESS
Status
colourRed
titleSTALLED
Status
colourGreen
titledecided
Page Properties
label

Status

Status
colourYellow
titlenot startedin progress

Description

Access into Network Zone environment (Vanguard)

Decision

Owning group

Implementation Coordinators (SILS-IC-L@listserv.ucop.edu)

Approver

Stakeholders

R =
A =
C =
I =

Decision-making process

Priority

Due date

Recommendation

Background

Alma (including network zone) requires a 3rd party authentication to login to the system. In order to login to the Alma network zone, the site (campus or CDL) 's authentication will need to integrate with the NZ. All sites that should have access into the NZ environment will need to have their authentication integrated with the NZ.

Dependencies

UCOP (CDL) and UCSD (SCP) staff manage UC-wide services; both sites need authentication within the NZ. (may depend on SCP, SFX, and related resource records handling for eResource records in NZ )

Single UC-wide patron record database or separate institutional patron databases? (PDCG) : if there is a shared patron database in NZ, this may require more sites (besides CDL & UCSD) to have access to the NZ

how many authentication integrations can NZ have? (posed to ExL May 8 ; answer May 14 ): “technically feasible, but has not been attempted; will double config & maintenance for campus IdP; will double config time for ExL”

any conflicts arising from same authentication integrated at both IZ & NZ (for non-UCOP sites) ExL answer May 14: will double config & maintenance required for campus IdP; (question to pose to campus IdP for those wanting access to NZ): limitations / conflicts within campus IdP depends on campus system.

Answer needed for “3rd party integrations” due to ExL May 29th.

Questions to consider

Who (aside from those staff directly managing UC-wide services), if any, should have direct access to network zone instance?

ExL’s list of tasks requiring access to NZ environment

Consider if any required tasks could be accomplished in IZ (not requiring direct access to NZ, eg. updating shared NZ bibliographic records can be done in IZ)Use UCOP ITS “Shib proxy” (connects all UC shib directories into one interface) for NZ authentication.

Background

Authentication for accounts to NZ could use either Shibboleth or Ex Libris Identity Service authentication method. Since CDL’s main office is split between those with Shibboleth accounts at UCOP and Shibboleth accounts at UCSD, authentication into the NZ needs to support both types of users. Shibboleth login is more secure and would support SSO for staff logging into the NZ. The UCOP ITS’s Shibboleth proxy service would enable a single integration point with Alma for all UC Shibboleth sites, negating the need for campus Shibboleth services to integrate with both their campus IZ and the NZ.

Dependencies

Questions to consider

Assumptions

Scenarios

Action Log

Action/Point Person

Expected Completion Date

Notes

Status

...