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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi! I was curious how people feel about the fact that we have separate two-factor authentication steps for both our Atlassian accounts and our BitBucket sub-accounts. It's not clear to me whether this is an intentional policy, or just a vestigial schism from before Atlassian implemented their cross-product SSO. On one hand, I suppose I shouldn't complain about anything that improves account security, which this technically does. On the other hand, it kind of undermines the purpose of SSO & having an integrated account, and it also adds to the chronic difficulty of managing multiple accounts.
I do realize I could simply turn off 2FA on the BitBucket side. This isn't a support question, I'd just like to understand Atlassian’s intention & ultimate goals for account security and authentication.
Why two OTP codes for one platform. It is very confusing and not user friendly.