![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/note-icon.png\"){kind=icon}
<\/p><\/div>
As of March 15, 2021, Atlassian administrators will need to configure an authentication policy or policies as appropriate to their environment to enforce logins through SAML. See Atlassian’s SSO article<\/a> for more information.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n Prerequisites<\/strong><\/p>\n\n\n\n Important Considerations<\/strong><\/p>\n\n\n\n Attribute Considerations<\/strong><\/p>\n\n\n\n The IdP URL<\/strong> will default to https:\/\/sso.jumpcloud.com\/saml2\/atlassiancloud<\/kbd> if this is not modified. This field is NOT editable after clicking Save Application<\/strong> and the connector will not work. You will have to delete and recreate the connector with the correct IdP URL for your site.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n The certificate.pem will download to your local Downloads<\/strong> folder.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n By default, users are created in the local directory in Atlassian Cloud. To grant them access to SSO, you need to move the users to the directory created for SSO with the verified domain. <\/p>\n\n\n\n Users are implicitly denied access to applications. After you connect an application to JumpCloud, you need to authorize user access to that application. You can authorize user access from the Application Configuration<\/strong> panel or from the Groups Configuration<\/strong> panel. <\/p>\n\n\n\n To learn how to authorize user access from the Groups Configuration<\/strong> panel, see Authorize Users to an SSO Application<\/a>.<\/p>\n\n\n\n This varies by SP.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n The attributes required for JIT provisioning are already included for SAML\/SSO authentication. <\/p>\n\n\n\n The Client ID and Secret (token) may only be shown once. Copy them to a secure location, like the JumpCloud Password Manager<\/a>, for future reference.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n Users are synced to sites and products in your organization. When you provision users to an organization, you need to grant them access to products. You can do this after you add a site for a product.<\/p>\n\n\n\n\n
\n
\n
Creating a new JumpCloud Application Integration<\/strong><\/h2>\n\n\n\n
\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/important-icon.png\"){kind=icon}
<\/p><\/div>\n
\n
Configuring the SSO<\/strong> Integration<\/strong><\/h2>\n\n\n\n
To configure JumpCloud 1<\/strong><\/h3>\n\n\n\n
\n
Download the certificate<\/strong><\/h4>\n\n\n\n
\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/tip-icon.png\"){kind=icon}
<\/p><\/div>To configure Atlassian Cloud<\/strong><\/h3>\n\n\n\n
\n
\n
\n
To configure JumpCloud 2<\/strong><\/h3>\n\n\n\n
\n
Granting User Access to SSO<\/strong> in Atlassian Cloud<\/strong><\/h2>\n\n\n\n
\n
Authorizing User SSO Access<\/strong><\/h2>\n\n\n\n
To authorize user access from the Application Configuration panel<\/strong><\/h3>\n\n\n\n
\n
Validating SSO user authentication workflow(s)<\/strong><\/h2>\n\n\n\n
IdP-initiated<\/strong> user workflow<\/strong><\/h3>\n\n\n\n
\n
SP-initiated<\/strong> user workflow<\/strong><\/h3>\n\n\n\n
\n
<\/p><\/div>\n
Using JIT Provisioning<\/strong><\/h2>\n\n\n\n
To complete the provisioning process:<\/strong><\/h3>\n\n\n\n
\n
Configuring the Identity Management Integration<\/strong><\/h2>\n\n\n\n
To configure Atlassian Cloud<\/strong><\/h3>\n\n\n\n
\n
![](\"\/wp-content\/themes\/jumpcloud\/assets\/images\/gutenberg-blocks\/warning-icon.png\"){kind=icon}
<\/p><\/div>Make sure you have a site in your organization<\/strong><\/h4>\n\n\n\n