Our attribute release policy allows basic directory attributes, employee attributes, eduPerson attributes, and group memberships used for IDP-level authorization to be released by default to each Service Provider.
Click here to view all of the available attributes associated to your Entra ID account.
These attributes (or claims) are provided by default to all new Enterprise Applications (or service providers):
| Attribute Name | Description | Example Value |
| Basic Directory Attributes |
||
| userPrincipalName | unityid@ncsu.edu | jqpublic@ncsu.edu |
| uid | unityid | jqpublic |
| givenName | first name | Jonathan |
| sn | last name | Public |
| displayName | preferred full name | Jon Public |
| unity email address (not preferred email or alias) | jqpublic@ncsu.edu | |
| employeeId | numeric campus ID | 000123456 |
| Employee Attributes |
||
| jobTitle | Position description of employee | Web Systems Programmer |
| departmentName | Department the employee is affiliated with | Shared Services |
| costCenter | Primary OUC (6 digit) | 517101 |
| division | Division name (2 digit) | Ofc of Information Technology |
| eduPerson Attributes |
||
| eduPersonPrincipalName | unityid@ncsu.edu | jqpublic@ncsu.edu |
| eduPersonPrimaryAffiliation | One of: student, staff, faculty, affiliate, separated | student |
| eduPersonAffiliation | one or more of (member, student, employee, faculty, staff, alum, affiliate, separated) | student; member |
| eduPersonScopedAffiliation | affiliation + @ncsu.edu | student@ncsu.edu; member@ncsu.edu |
| Other attributes | ||
| memberOf | list of Entra ID groups assigned to the Enterprise Application that the user is a member of | CN=NCSU-J-Unity Users,OU=Managed Groups,OU=NCSU,DC=wolftech,DC=ad,DC=ncsu,DC=edu;... |
Additional attributes may be included based on the needs of specific application vendor integrations. If you need additional non-default attributes (like a vendor-specific tenant ID), please include that in the SSO Request.
For those applications that are making use of InCommon federation with Entra and Cirrus Bridge the attributes that are being passed are being passed using both the FriendlyName and the urn:oid formats.
| Attribute Name | Description | Example Value |
| pairwise-id | unique, persistent, pseudonymous scoped identifier | Z6NB6RRDEADBEEFBEEFLJ2YU67C65WHTUT673YBZX ABACABDCCAA@ncsu.edu |
| urn:oid formatted attributes | ||
| urn:oid:1.3.6.1.4.1.5923.1.1.1.1 | urn name of eduPersonAffiliation | student; member |
| urn:oid:1.3.6.1.4.1.5923.1.1.1.5 | urn name of eduPersonPrimaryAffiliation | student |
| urn:oid:1.3.6.1.4.1.5923.1.1.1.6 | urn name of eduPersonPrincipalName | jqpublic@ncsu.edu |
| urn:oid:1.3.6.1.4.1.5923.1.1.1.9 | urn name of eduPersonScopedAffiliation | student@ncsu.edu; member@ncsu.edu |
| urn:oid:0.9.2342.19200300.100.1.1 | urn name of uid | jqpublic |
| urn:oid:2.16.840.1.113730.3.1.241 | urn name of displayName | Jon Public |
| urn:oid:0.9.2342.19200300.100.1.3 | urn name of mail | jqpublic@ncsu.edu |
Note: This article uses a significant amount of terminology related to Identity and Access Management, please refer to the Identity and Access Management glossary reference if needed.