UCI Use CampusID for Tracking Identity¶

Scope: UCI
Type: Standard
Version: 2025

Goal¶

Ensure that services are resilient to changes in UCInetIDs.

Ownership¶

Direct questions to the Owner: TBD email redacted

Resources to comply with this standard should be directed via the Executive sponsor: TBD email redacted

Timeline & Enforcement¶

All services must be compliant with this standard by July 1, 2026

Exception Process¶

Exceptions can be granted by the Director overseeing the project. Exceptions must include an explanation for why the standard can not be followed. Exceptions must be registered with the ARB, and renewed every year.

Terminology¶

• UCInetID is a human-readable identifier for a person associated with UCI. They are most easily found as the “local” part of the person’s email address, before the @ sign. This identifier can change over time (eg when the person’s name changes).
• CampusID is a numeric identifier for a person associated with UCI. They take the form of a persistent and unique 12-digit integer number that will not change over the course of that person’s association. All students, faculty, staff, and sponsored accounts at UCI have a CampusID.
• Campus Attributes is the set of attributes associated with a given CampusID by OIT, including their UCInetID, name, and other information.
• Service Attributes is the set of attributes associated with a given CampusID by a particular service.
• The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119

Requirements¶

Scope¶

1. All services that track users are in scope of this standard
2. Unless the service anonymises all user tracking

Prioritize CampusID¶

1. Services MUST use CampusID to associate their Service Attributes with a set of Campus Attributes
2. Services MAY mirror additional fields from the Campus Attributes into the Service Attributes to make the account easier to work with, but MUST update these mirrored fields to reflect changes in the Campus Attributes
3. Services MAY track additional fields in their Service Attributes that do not correspond to fields in the Campus Attributes
4. Access grants to Service Identities MUST rely on the CampusID
5. This ensures that grants are resilient to changes of any aspect of the Service Attributes or Campus Attributes
   1. UCInetID may change over the course of an account lifetime
6. This avoids reclaimed UCInetIDs from inheriting permissions from older owners of that ID

References¶

• Identity Management
• CampusIDs: A Developer’s Guide