Okta/SSO/SCIM - Choosing a custom property for username?

[Tariq Ahmed]

Hi all,

At the moment, our Jira username is mapped to the Okta username.

Is it possible to configure Jira to use a custom property for the username?

Thanks!

[Craig Castle-Mead]

Hey Tariq,

I've only got experience with the Atlassian native DC SAML plugin - so not sure what you're using. The below is purely my understanding as it stands at the moment. 

I believe NameID  is the default SAML username property exposed by Okta/SAML in general. If the field you're wanting to use as the username is already being exposed via the Okta app auth process, then with the native integration, you should be able to change the "Username mapping*" value from ${NameID} to the field you want to use. 

We've just recently changed our SAML integration from using the Okta email address to the Okta username, and we approached that by updating the NameID mapping on the Okta side so that NameID exposed - https://support.okta.com/help/s/question/0D51Y00005rbRzCSAU/how-do-i-set-it-so-application-username-is-firstnamelastname?language=en_US has an overview to change to firstName + lastName, but change the custom mapping to be the field(s) you want - eg: user.username 

FYI - I've found https://chrome.google.com/webstore/detail/saml-chrome-panel/paijfdbeoenhembfhkhllainmocckace?hl=en to be helpful in understanding what fields/values are being exposed during the SAML process.

CCM