SAML Attribute Mapping for OKTA Users: Display Name is Not Used

Problem

Display names for OKTA users are not correctly displayed in JetBrains License Vault after logging in via SSO.

Cause

The issue arises because the displayName attribute mapping in Hub's SAML authentication module was configured incorrectly. Instead of using the displayName attribute from OKTA's SAML assertion, the system was defaulting to the username (email prefix) as the display name.

Resolution

To resolve this issue, update the attribute mappings in Hub as follows:

• Navigate to Hub → Auth Modules → Alarm Okta (SAML 2.0) → Attributes.
• Set the following attribute mappings:
  • Username: Use a stable, unique attribute such as OKTA login or email.
  • Email: Map to email.
  • First Name: Map to firstName.
  • Last Name: Map to lastName.
  • Full Name: Map to displayName.

For detailed guidance, refer to the JetBrains documentation on SAML attribute settings.

After making these changes:

• Verify that display names are correctly set for new users logging in through SSO.
• If duplicate accounts exist due to legacy mismatches, you can use the user account merging functionality to unify them.