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,460,632
Community Members
 
Community Events
176
Community Groups

[Atlassian access] OKTA SSO only on a subset of users

Hi everybody, 

I have searched a lot for this topic, but I could not find a good answer anywhere.

I have an Atlassian Jira Cloud environment and now every user is created in Jira and access using email and password.

I am investigating the Atlassian Access package, considering to implement SSO with OKTA and/or enforce 2FA, (I am not planning to provision users via OKTA).

Question: is it possible to enable SSO only for a subset of users(e.g. internal users), and have other users access with username and password?

 

Thank you very much

Have a nice day,

Luca

 

 

1 answer

1 accepted

2 votes
Answer accepted

Hi Luca, 

Thanks for using Atlassian Community.  

For a short answer, you can only enable SSO via Okta to the internal users in your Jira site. When you integrate with Okta, the 2FA feature on Okta side will be used. 

To give more context on that :

Atlassian cloud uses a centralized identity service in https://id.atlassian.com. Here, an end user will have a single account identified by a unique email address. That account is the user's online identity and access into different cloud sites are granted on that account. 

On Jira cloud side, the owners of the site controls which Atlassian Accounts gets access to their site. 

Atlassian Access allows organizations to claim ownership of Atlassian Accounts in that centralized identity service. When you claim your company's domain in Atlassian cloud, you effectively take ownership of all Atlassian Accounts with an email address under your company's domain. You can then further enforce SSO via Okta to those accounts. 

On the Jira cloud site, only accounts under your company's domain will be enforced to login via Okta. These accounts are effectively your internal users. The rest will keep using the default Atlassian Account login password or any SSO that their own organization may have enforced on Atlassian Cloud.

There are 2 admin hats in play here. 

  1. Organization Administrators : Manages the domain Atlassian Accounts and SSO for Atlassian Cloud. 
  2. Site Administrators : Controls who get access on the Jira site. They can grant access to both "internal" and "external" users. 

Here is the login experience for the users :

  • A user will try to reach any site on Atlassian Cloud (ie. your jira site)
  • The user will need to login via https://id.atlassian.com
  • The user will identify with an email address in login form.
    • If the email address is under your company's domain, the user will be redirected to Okta for authentication. This includes 2FA if that is enabled on Okta side.
    • If the email address is not under a claimed domain, the user will authenticate using the Atlassian Account Password. 
  • After authentication, the user will be redirected back to the Jira site. If the account was granted access, the application will load otherwise a permission error is returned. 

I hope this helps. 

 

Cheers,

Ramon

Thank you very much for the explanation.

Cheers,

Luca

No worries Luca and good luck!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events