...
Move to ID → Application → Enterprise Application and click Atlassian Cloud. Then select Single Sign-On settings below.
Scroll title | ||
---|---|---|
| ||
Click on SAML in the SSO method selection.
...
16. Click Unique user ID.
Scroll title |
---|
1517. Atlassian Atlassian Cloud requires a name identifier (a unique user identifier) to be mapped to the user's email (user.email).
If you have M365, edit the original attribute change it to user.mail, and save it.
...
Code Block |
---|
attribute and claim givenname user.givenname surname user.surname emailaddress user.mail name user.userprincipalname 고유한 사용자 ID user.userprincipalname |
1618. Once you're done setting up, press the Test SSO button to verify that it works.
Scroll title | ||
---|---|---|
| ||
1719. Now, back in Guard, click Next and select the domain you want to associate with the IdP.
Scroll title | ||
---|---|---|
| ||
1820. You're done configuring SAML, click “Stop and save SAML”.
...
Read the prompts and click Next.
Scroll title | ||
---|---|---|
| ||
23. Copy the generated SCIM base URL (1) and API key (2).
...
Warning |
---|
The API key is not stored, so be sure to copy it somewhere safe. |
34. Log in to the Microsoft Entra Admin Center and click on “User Account Prospecting”.
Scroll title | ||
---|---|---|
| ||
45. On the “Identity Lifecycle Automation” screen, click the Start button.
Scroll title | ||
---|---|---|
| ||
56. On the Credentials screen, copy the directory base URL(1 ) created by Guard in step 1 to “Tenant URL”, paste the API key(2 ) into Secret Token, click Test Connection, and then click Save.
Scroll title | ||
---|---|---|
| ||
67. Once provisioning starts, check the “Provisioning log” to make sure it's working properly.
Tip |
---|
See also |
...