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,456,929
Community Members
 
Community Events
176
Community Groups

Google SSO

Instructions for Multi-factor Authentication generally tell me that if Google accounts are used to log into Atlassian products, MFA/2FA should not be used in Atlassian user settings, but instead in Google user management.  

My question is where can I tell which users use Google SSO and which do not? If users use Google SSO with native Google MFA, what is preventing them from also logging in with the native Atlassian account which is still active, and not using MFA?

Our Atlassian admin.atlassian.com page is still the old setup with limited User and Group interface.  What I'm referring to is, we aren't yet migrated to the new feature described here: User management for cloud admins just got easier.  Atlassian is migrating customers since January 2021 but it looks like it is taking longer than planned.  

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events