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.
We have an organization, a verified domain, and claimed accounts.
We'd also want to invite users from outside of our organization (domain) to access and be part of our Confluence Cloud instance.
As we'd like access to our data to be as secure as possible, is there a way to enforce them to have 2FA enabled?
- Something like.. if this user doesn't have 2FA enabled AND isn't logged with OAuth(Google, AD, etc), don't allow them to access our instance.
Hi @Andrei,
Welcome to the Community!
I'm pretty sure that that only way to enforce 2FA would be to create "contractor" accounts in your organization. I don't think Access allows to to control anything with accounts outside your organization.
I hope that helps answer your question.
-Jimmy
Thank you for your quick response.
You're right. Documentation says it's not possible, only for managed accounts (with verified domains).
I'm thinking it still might be useful to do a check for users that are invited via email or already have an Atlassian account.
A check that tells me if the user has 2FA enabled. I can then choose not to allow access to my Confluence instance unless they do.
Sharing my Conf instance is compromised if they have an easy to guess pass and no 2FA.
Thoughts? Do you know if something of the sort might be in Atlassian's pipeline?
Andrei.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Andrei,
Looks like it's something that has been reported at the very least:
https://jira.atlassian.com/browse/ACCESS-797
I'd recommend commenting on that issue with your specific use case details, and voting for and watching that issue for updates.
-Jimmy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We're currently planning to implement visibility into which users on your site have enabled 2FA relatively soon (ACCESS-797). We do have a plan for supporting actual enforcement of mandatory 2FA on external accounts; however this is going to take quite a bit longer. Follow ACCESS-102 for that one.
Thanks!
Dave
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's great news! I'll follow both of them. As soon as it gets done, I'll get customers back on board to Access...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just an update it's already on cloud roadmap
https://www.atlassian.com/wac/roadmap/cloud?search=unmanaged%20user%20security
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.