Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,465,224
Community Members
 
Community Events
176
Community Groups

Configure SAML for Atlassian with Okta

Hi,

We are about to enable SSO with Okta in Atlassian.

At this point, we manage two environments in Atlassian, which means the users in Jira/Confluence are not the same as the users in Bitbucket.

In the setup guide, I saw we need to subscribe to Atlassian Access.

My question is if we'll subscribe to this app it will work on both the environments - Bitbucket and Jira/Confluence? 

 

Thank you! 

1 answer

1 vote

Hi @Iris Ayelin,

If both Jira/Confluence users and Bitbucket users have an account with an email from one of your verified domains, then SAML SSO can be enforced for all of them. However, it is also possible to enforce SAML SSO for some users and not for others.

If you subscribe to Atlassian Access, there will be an option in https://admin.atlassian.com/ (for Org Admins) called Authentication policies. You'll need to configure and save SAML and then enforce SAML single sign-on in an authentication policy.

In case you want to enforce SAML SSO for some users but not for others, you can have two authentication policies: one with the setting Enforce single sign-on disabled, and another one with this setting enabled. You can then add different users to each of these policies.

Otherwise, you can use one authentication policy with Enforce single sign-on enabled, and all users will need to log in with SAML SSO.

You can take a look at the following video for a brief introduction to Authentication policies:

Here are some links from our documentation:

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events