Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

2-Step Verification and SAML SSO

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?

1 answer

0 votes

Hello TB,

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.

- Enforced two-step verification

So, you just need to enable 2FA on your identity provider, it’s not necessary to enable anything on Atlassian access.

Regards,
Angélica

Thank you Angélica.  Currently we have user created in Jira but once we enable SAML SSO, can you have the same user that was created in Jira and SSO co-exist?

 

Thanks,

Tien

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.

So for example if the Identity provider is down, can the user still authenticate locally to Jira?

I just want to make sure, SAML Version 2.0 is supported with Jira, right?

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.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Atlassian Access

We're launching improved navigation for admins

Hi Atlassian Community, My name is Avni Barman and I am a Product Manager on the Atlassian Access team! One of my top priorities is to help make the administrator's life easier through improved pro...

1,088 views 2 12
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you