Below is a list of attributes (claims) that the IdP must configure and send to Cyber Guru via SAML assertion during authentication. The values to be used refer to any LDAP system. For the attribute names of the LDAP used by the Identity Provider, refer to its guide.
|
⚠️ |
Any other attribute the client wishes to use, not present in the list, must be discussed in advance with Cyber Guru |
Attribute: username
Value: Unique identifier
Optional / Mandatory: Mandatory
Notes: Unique identifier within the Cyber Guru platform for the Client's tenant. It is used as a key for user association and cannot be changed once the project is underway. The client must use a user profile field that is unchangeable (e.g., in Active Directory, ObjectGUID)
Update: On first access
Attribute: firstName
Value: User's first name
Optional / Mandatory: Mandatory
Notes: Usually identified with user.givenName
Update: On every access
Attribute: lastName
Value: User's last name
Optional / Mandatory: Mandatory
Notes: Usually identified with user.surname
Update: On every access
Attribute: email
Value: Email
Optional / Mandatory: Mandatory
Notes: The user's email. Usually identified with user.mail
Update: On first access. In specific cases where the user's email might change over time, a configuration of "On every access" can be set
Attribute: locale
Value: Two-letter lowercase ISO code of the user's language (e.g., "en")
Optional / Mandatory: Optional
Notes: Client's system language
Update: On first access
Attribute: country
Value: Two-letter uppercase ISO code of the user's country (e.g., "US")
Optional / Mandatory: Optional
Update: On first access
Attribute: Team (*)
Value: Name of the team
Optional / Mandatory: Mandatory if not preloaded
Notes: It is the name of the team (or department) within which the user must be placed for statistics and gamification purposes. Teams that differ by even one character are considered different teams. If the team is valued in the user preload, then this attribute should not be considered.
Update: On every access
Attribute: Org_{Org Name1} (**)
Value: Org Name 1
Optional / Mandatory: Optional
Notes: Organization 1 to which the user belongs
Update: On every access
Attribute: Org_{Org Name2}
Value: Org Name 2
Optional / Mandatory: Optional
Notes: Organization 2 to which the user belongs
Update: On every access
Attribute: Org_{Org NameN}
Value: Org Name N
Optional / Mandatory: Optional
Notes: Organization N to which the user belongs
Update: On every access
In particular:
(*) The choice of the team used for gamification purposes must consider the number of users within the various teams. Teams with 5 vs 100 users could affect the balance of the competition (team scores are calculated based on the average scores of their members).
If the "team" of belonging is defined with another category, different from the one contained in the LDAP and preloaded in the platform, then the "Team" field should not be valued or configured within the SP response. Team updates and new users must necessarily be handled with a user list. In defining teams, the previously mentioned cardinality should be considered.
(**) The Organization attributes refer to further classifications of users, for example, Organizational Unit, location, City, age group, etc. These classifications can be used on the platform as filters in dashboards and reports.