-
Suggestion
-
Resolution: Duplicate
-
None
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.
- duplicates
-
- Closed
[ACCESS-116] Users should be able to choose which domain to enable MFA/2FA on
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
| Link |
New:
This issue duplicates |
| Component/s | New: Flexible Auth [ 61297 ] |
| Labels | Original: Flex-Auth |
| Remote Link | New: This issue links to "Page (Confluence)" [ 480579 ] |
| Description |
Original:
{panel:title=Seeking feedback on our solution}
The product team is looking to speak with a few customers to get feedback on a solution we are designing for this problem. These sessions will be *30 mins long* and will be conducted in the *week of Feb 24-28*. If you are interested in giving feedback, *please email* [*sshaheed@atlassian.com*|mailto:sshaheed@atlassian.com] *with your timezone and few preferred 30 min slots* during the week of Feb 24-28. As a token of our appreciation, we will provide a $50 USD gift voucher for interview participants. {panel} h3. 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. |
New:
h3. 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. |
| Comment |
[ {panel:title=Seeking feedback on our solution}
The product team is looking to speak with a few customers to get feedback on a solution we are designing for this problem. These sessions will be *30 mins long* and will be conducted in the *week of Feb 24-28*. If you are interested in giving feedback, *please email* [*sshaheed@atlassian.com*|mailto:sshaheed@atlassian.com] *with your timezone and few preferred 30 min slots* during the week of Feb 24-28. As a token of our appreciation, we will provide a $50 USD gift voucher for interview participants. {panel} ] |
| Labels | New: Flex-Auth |
| Remote Link | New: This issue links to "Page (Confluence)" [ 471201 ] |
| Description |
Original:
h3.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. |
New:
{panel:title=Seeking feedback on our solution}
The product team is looking to speak with a few customers to get feedback on a solution we are designing for this problem. These sessions will be *30 mins long* and will be conducted in the *week of Feb 24-28*. If you are interested in giving feedback, *please email* [*sshaheed@atlassian.com*|mailto:sshaheed@atlassian.com] *with your timezone and few preferred 30 min slots* during the week of Feb 24-28. As a token of our appreciation, we will provide a $50 USD gift voucher for interview participants. {panel} h3. 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. |