Filtering and transformation (API Connectors)

See additional explanation under the screenshot below:

Open

When synchronizing users and groups from the cloud based identity providers you may want to specify some details about how they are synced. You may specify on this page what users and groups should be synced as image above shows. You can also select if Member users, Guest users or both should be synced.

Username selection (since Kantega SSO 6.29.0 and 7.29.0)

K-SSO supports to select other username formats than the standard userPrincipalName. For Entra ID only you may use sAMAccountName as an alternative. If some users do not have this value userPrincipalName will be fallback.

For all IdPs you may select to use email as the username attribute to sync. This means that when you sync both username and email fields will contain the email address. This can be convenient if situations where the IdP operates with userPrincipalName values that is somewhat cryptical/unreadable.

Note that in situations where the same email is synced for more than one user, userPrincipalName will be used for all these users instead as a fallback to avoid duplicates. In rare situations where userPrincipalName is not present during sync, email will be used as fallback if this is present.

Username format

You may also transform the incoming usernames using regular expressions (or to select Use Name-part in the Transformation drop-down to get what is right of the @ symbol in the username). By using many regular expressions in the right priority you may transform complex username formats in your identity provider to match the username formats you would like to have (or that you already have from before) in your Atlassian product.

You may also use the Test transformation section to test your regular expressions for different user names.