Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-116

Users should be able to choose which domain to enable MFA/2FA on

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Summary

      Currently enabling MFA/2FA from the organization page will enable it for all domains that are verified under the organization. If user only want certain domains or users to have 2FA, this is currently not possible. Adoption of MFA/2FA is quite difficult due to the absence of fine-grained configuration.

      While it is possible to exempt per uses basis after the MFA activation, it is still not very feasible to exempt it one user at a time if there are a lot of users that needs to be exempted. There is also no way to track from JIRA which users are exempted as well so organization admins will have to keep an external record on which user is exempted.

            [ACCESS-116] Users should be able to choose which domain to enable MFA/2FA on

            Chris Funderburg added a comment - - edited

            I'd clarify that the whole feature, as designed, seems useless for everyone but very small organisations.  A company of over 300 users can't enable forced MFA all at once as that's a support nightmare - and there appears to be no way to enable it for your existing users individually.   

            Chris Funderburg added a comment - - edited I'd clarify that the whole feature, as designed, seems useless for everyone but very small organisations.  A company of over 300 users can't enable forced MFA all at once as that's a support nightmare - and there appears to be no way to enable it for your existing users individually.   

              njayasankar@atlassian.com Narmada Jayasankar
              vchin Vincent Chin (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: