We standardize on the following IdM generated identifiers for use across the University. This will simplify the experience of members of the University community when accessing services.
The NetID is the single identifier a person needs to know. It is the unique identifier for students, faculty, staff, and other affiliates of the University to access information online, as well as to identify themselves on forms and paperwork.
NetIDs is preassigned using the person’s initials and a collision number. (Existing NetIDs will be grandfathered, so no changes will be required for current affiliates who have selected NetIDs.) We made this change to simplify the process of provisioning services for new affiliates, and to address “exhaustion” of the self-selected NetID space. (Most common NetIDs have already been selected, making it harder for new affiliates of the University to find acceptable NetIDs.)
A facility for self-selecting University email addresses will decouple NetID from email delivery. This will allow login information to not be revealed when providing an email address, as well as allowing email addresses to more closely resemble a person’s name.
The RCPID is the single unique identifier for communicating from system to system. Nobody will ever need to know their RCPID, it exists simply to facilitate the collation of records across systems. Why not just use NetID? A NetID can be changed under certain circumstances. By using RCPID instead, systems can isolate themselves from these changes.
The External ID is the single unique identifier for communicating from system to system. But used mainly with 3rd party services such as Cloud (SaaS) . Similar to RCPID, Nobody will ever need to know their ExternalID, it exists simply to facilitate the collation of records across systems.
RUconnection Card Number (RCN)
A new, random number was introduced to enhance the security of the RUconnection ID card. RCNs is unique to a given card, and will change completely if a card is lost or replaced. Systems that use the ID card will need to translate from the RCN to identify the person in question. In addition to the RCN , there are also other unique identifiers attached to the Id Card such as the Bar code and the CVC number.
Source System Identifiers
These are the identifiers generated by other than IdM system such as HR and Students systems. It is strongly recommended that services use the IdM identifiers as mean for system to system communication as source systems identifiers specific to vendors can change from time to time based on the selected ERP system.
The RUID is the single unique identifier generated by the main Rutgers’ Student system (SRDB) .
The EMPLID is the single unique identifier generated by the HR system (PeopleSoft) .
ANUMBER is the single unique identifier generated by the RBHS student system (Banner). It was also the identifier for RBHS employees before migrating to the single Rutgers HR system.
PIDM is the secondary unique identifiers generated by the RBHS student system (Banner). It was also the identifier for RBHS employees before migrating to the single Rutgers HR system.
|NetID||Semi-Private||Known only by the user (Rutgers is moving to using affinity name in email instead of NetID)|
|RCPID||Private||Should not be displayed to the end user
used as system to system integration identifier for internal systems ONLY.
NOT TO BE RELEASED OUTSIDE of Rutgers
|External ID||Private||Should not be displayed to the end user
used as system to system integration identifier for externally-hosted/Cloud-based applications.
|RUID||Semi-Public||SRDB ID for students. Students, Registrar, and faculty members have knowledge of student IDs|
|EmplId||Private||PeopleSoft ID for employees|
|A#||Semi-Public||Banner ID for RBHS students. Users have knowledge of this ID. RBHS Registrar and faculty members have knowledge of the student IDs|
|PIDM#||Private||Banner ID for RBHS students.|
|RCN||Private||NOT TO BE RELEASED OUTSIDE of Rutgers|