You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I see Atlassian is recommending that we use our own identity provider for 2-Step Verification. Is there instruction as how to enable that when turning on "enforcing 2-step verification" in Atlassian access?
Welcome to Atlassian Community!
The option to enforce two-step verification it’s great when users are not managed because it’s possible to force them to enable this option on their profiles.
In your case, as users are using SAML to log in, we don’t recommend using the option to enforce 2FA.
Enforce two-step verification
We recommend that you don’t enforce two-step verification if your users log in through Google or with SAML single sign-on.
Two-step verification and Google or SAML SSO
Users who log in to your Atlassian Cloud products with Google or SAML single sign-on don't see Atlassian two-step verification. We recommend that you use Google's or your identity provider's equivalent instead.
Our rationale for this is that using Google or a SAML provider to log in with is choosing a non-Atlassian identity provider and we therefore believe that it's best to complete your entire login with the one provider, including using that provider's two-factor authentication (2FA) solution.
So, you just need to enable 2FA on your identity provider, it’s not necessary to enable anything on Atlassian access.
If the user has the same email on Jira and on the Identity provider, it will be synced, so this account will show on both. It's important that the user exists on the Identity provider because it's the users in the IDP that will be created in Jira and not the opposite.
When the Identity provider is down, users can use the option “Can’t login?”, so they will receive an email to set the Atlassian account password and they will be able to log in.
SAML 2.0 is supported, you can configure it for your Atlassian site.