Provision and sync users from an identity provider
Make changes in your identity provider to users and groups and sync them to your Atlassian organization.
If you want to add a public name to an Atlassian user profile, you can include the attribute from your identity provider and synchronize the user to your Atlassian organization. This enables the public name to appear in the Atlassian user's profile.
To map an attribute for Okta:
Go to Atlassian Cloud app in Okta.
Switch to the Provisioning tab.
From the left hand pane, under Settings select To App.
Under Atlassian Cloud Attribute Mappings, select Go to Profile Editor.
Select Add Attributes. Depending on the attribute that you want to add, enter the following values.
For nickname:
* Variable name: nickName
* External name: nickName
* External namespace: <namespace> urn:ietf:params:scim:schemas:core:2.0:User
For location:
* Variable name: basedIn
* External name: basedIn
* External namespace: urn:scim:schemas:extension:atlassian-custom:1.0:Attributes
Save the attribute.
Select the Mappings button.
From the top menu select Okta User to Atlassian Cloud tab.
Under Okta User User Profile section, select the variable name for the attribute you added.
Select nickname and map it to the nickname attribute you created.
Select location and map it to the basedIn attribute you created for location.
If no location attribute exists, you can create your own.
Select Save Mappings.
If you want to set up a mapping for a user’s location, use an existing location attribute. If there’s no location attribute, create one first. To create a location attribute:
Go to Atlassian Cloud app in Microsoft Azure AD.
Select Provisioning.
Under Edit provisioning, select Mappings and select Provision Microsoft Entra ID Users.
Under Attribute Mappings, select Edit attribute list for AtlassianCloud.
For the attribute name, enter urn:scim:schemas:extension:atlassian-custom:1.0:Attributes:basedIn.
Save your changes.
To map an attribute for Microsoft Azure:
Go to Atlassian Cloud app in Microsoft Azure AD.
Select Provisioning.
Under Edit provisioning, select Mappings and select Provision Microsoft Entra ID Users.
Under Attribute Mappings, select Add New Mapping. For each mapping you want to add, enter the following:
For nickname:
* From Source attribute, select Public Name.
* From Target attribute, select nickName.
For location:
* From Source attribute, select physicalDeliveryOfficeName.
* From Target attribute, select urn:scim:schemas:extension:atlassian-custom:1.0:Attributes:basedIn.
Save your changes.
To map an attribute for OneLogin:
Go to Atlassian Cloud app in OneLogin.
Select Parameters.
Under Optional Parameters select Nickname.
From the attribute that you’re using for location, map it to urn:scim:schemas:extension:atlassian-custom:1.0:Attributes:basedIn. If there’s no location attribute, create a new one with this mapping.
Select the source field.
Under Flags options, check Include in User Provisioning.
Save the changes.
Sync user to your Atlassian organization
In your identity provider:
Go to the profile of the user you want to sync the public name for to Atlassian
Add the value to the Source attribute you selected (for example mailNickname field)
Sync the user to Atlassian by assigning Atlassian Cloud App to user
In your Atlassian organization:
To check the user’s public name:
Ask user to log in to the Atlassian account
View the Profile and visibility page: https://id.atlassian.com/manage-profile/profile-and-visibility
Was this helpful?