UCI User Account Names¶

Scope: UCI
Type: Standard
Version: 2025

Goal¶

Improve audits, accounting, and user experience by unifying account names and email addresses used in systems and applications across UCI.

Ownership¶

Direct questions to the Owner: Warren Leung email redacted

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

Timeline & Enforcement¶

All services must be compliant with this standard by December 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¶

• Account Name/Username - A name based identifier referencing an account in a system or application. (ex: “daldrich”)
• UCInetID - An account used to access IT services provided by UCI.
• CampusID - A persistent, unique, 12-digit integer used to identify an individual person or entity across Account Name changes. All UCInetIDs have assigned.
• UCInetID Email Address - UCInetID@UCI.EDU address that is forwarded to an email mailbox.
• My.Name - An alternate email address alias based on a person’s full name.
• 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¶

This standard applies to all services that:

• Use local accounts instead of enterprise user authentication
• Track users by an account name rather than the preferred, persistent CampusID

Account Names¶

When a local account name is needed, services MUST:

• Use the UCInetID as the account name.

Services SHOULD NOT :

• Use the mail attribute (“published email”) as the account name.
• Reason: Users can change their published email to aliases that do not match their UCInetID.

If an email-format account name is required:

• eduPersonPrincipalName (ePPN) provides the string UCInetID@UCI.EDU
• businessEmail (ucinetid@uci.edu) is also an acceptable alternative.

Services MUST NOT:

• Use any other format for UCI member account names (e.g., first initial + last name, My.Name alias).

Handling UCInetID Changes¶

Services MUST:

• Update local account names whenever a UCInetID is changed.

Services MUST

• Be prepared to handle UCInetID changes.
• Services can track users by a persistent identifier such as:
  • CampusID (preferred)
  • Registrar ID
  • UCPath EmplID
  • Note: CampusID is preferred when available, as it supports people who switch between student and employee roles.