Considering migrating from Jira/Confluence/Crowd Server to Cloud, right now we host Jira, Confluence and Crowd...using Crowd Server for basic user/group management w/our on-prem AD.
Currently we use Azure AD Connect for hybrid-identity directory integration between our on-prem AD and AD Azure in the cloud. If we wanted to subscribe to Atlassian Access for SSO as part of the Server-to-Cloud migration effort, are there any exceptions/concerns when integrating Access with Azure AD while managing our users on-prem in AD and syncing to Azure using this Azure AD Connect agent (hybrid-identity management)?
Hi Megha,
When SAML single sign-on is configured, users won't be subject to Atlassian two-step verification provided by Atlassian Access even if 2FA is configured for your organization. This means that two-step verification is essentially "skipped" during the login process for users enabled for SAML Single sign-on.
We recommend that you use your identity provider's 2FA policy or any equivalent offering instead.
Refer "SAML single sign-on with two-step verification and password policy" section here :
https://support.atlassian.com/security-and-access-policies/docs/configure-saml-single-sign-on-with-an-identity-provider/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.