SSO Claim Mappings

SSO claim mappings allow us to control what attributes or transformations of attributes are given out to SSO integrated apps. See below for the currently support/approved ones.

Detailed Information

Username (as uid)

Example: "joseph.user"

Username (as cn)

Example: "joseph.user"

Department (as departmentNumber)

Example: "joseph.user"

User's displayName (Preferred "First" "Middle" "Last" as a full name)

Example: "Joe Allen User"

Student or Employee ID# (as employeeNumber)

Example: "0123456"

Group memberships (as isMemberOf)

Email Address (as "mail")

Example: "joe.user@maine.edu"

Student, Faculty, Staff, etc. (as eduPersonAffiliation)

Example: "staff"

Example: "student, member, staff, employee"

Primarily Student, Faculty, Staff, etc. (as eduPersonPrimaryAffiliation)

Example: "staff"

eduPersonScopedAffiliation

Example: "member@usm.maine.edu, student@usm.maine.edu, student@maine.edu, member@ums.maine.edu, member@maine.edu, staff@ums.maine.edu, staff@maine.edu, employee@ums.maine.edu, employee@maine.edu"

"First" name (usually as givenName)

Example: "Joseph"

"Last" or Family name (as sn)

Example: "User"

EPPN (eduPersonPrincipalName)

Example: "joe.user@maine.edu"

samlSubjectlD

samlPairwiselD

eduPersonUniqueld

Example: "TFHWE5GCZ2MHUCGQC4WG5SVWBQCWZ7JMK4UKNJ2HSC6QAKRAS7XA@maine.edu"

Other (specify in Description)

Environment

  • Shibboleth
  • CAS
  • Entra