You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. The Name ID attribute in Azure AD can be mapped to any desired user attribute by editing the Attributes & Claims section.
125
+
126
+
> [!div class="mx-imgBorder"]
127
+
> 
128
+
129
+
a. After clicking on Edit, any desired user attribute can be mapped by clicking on Unique User Identifier (Name ID).
130
+
131
+
> [!div class="mx-imgBorder"]
132
+
> 
133
+
134
+
b. On the next screen, the desired attribute name like user.userprincipalname can be selected as an option from the Source Attribute dropdown menu.
135
+
136
+
> [!div class="mx-imgBorder"]
137
+
> 
138
+
139
+
c. The selection can then be saved by clicking on the Save button at the top.
140
+
141
+
> [!div class="mx-imgBorder"]
142
+
> 
143
+
144
+
d. Now, the user.userprincipalname attribute source in Azure AD is mapped to the Name ID attribute name in Azure AD which will be compared with the username attribute in Atlassian by the SSO plugin.
145
+
146
+
> [!div class="mx-imgBorder"]
147
+
> 
148
+
149
+
> [!NOTE]
150
+
> The SSO service provided by Microsoft Azure supports SAML authentication which is able to perform user identification using different attributes such as givenname (first name), surname (last name), email (email address), and user principal name (username). We recommend not to use email as an authentication attribute as email addresses are not always verified by Azure AD. The plugin compares the values of Atlassian username attribute with the NameID attribute in Azure AD in order to determine the valid user authentication.
151
+
121
152
### Create an Azure AD test user
122
153
123
154
In this section, you'll create a test user in the Azure portal called B.Simon.
0 commit comments