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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello,
My organisation is an existing Bitbucket and Jira customer. We now plan to SSO enable Atlassian access for our employees. I am unsure what happens to a users' pre SSO account and privileges when the same user logs in with SSO credentials.
Will the user still be able to see their old repositories (I think not) ? If not, is there a way to map the pre SSO users' permissions to the new SSO user ?
Thanks.
-Avinash
Hello @Avinash Shenoy ,
Welcome to Atlassian Community!
When you enable the Atlassian Access SSO for your organization's managed accounts, you are just changing the way the users authenticate with the Atlassian Products (Jira, Confluence,Bitbucket, etc).
So when the users try to log in on Atlassian Products, instead of using the username and password, they will be redirected to your Identity Provider to complete the authentication.
All the user's permissions and groups they are part of on Atlassian products will continue the same. Bringing it to Bitbucket, the users will still be able to have access to the same repositories they had before SSO was enabled.
For further details on how to enable SSO for your Atlassian Organization, you can refer to Configure SAML single sign-on with an identity provider.
Thank you, @Avinash Shenoy !
Patrik S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.