-
Bug
-
Resolution: Fixed
-
High
-
None
-
19
-
Issue Summary
Org admins can't remove the 2FA for managed accounts when the user provisioning integration is on. The following message is displayed on the user's profile at the Org:
Two-step verification
Go to your identity provider settings to manage how users log in with a second step.
Environment
An Organization with user provisioning only and not SAML.
Steps to Reproduce
- A regular user enables Atlassian 2FA on their account
- The org admin enables user provisioning, including the user above
- The user (now managed entirely by the IDP) loses their phone
Expected Results
The org admin should be able to disable 2FA for that user, since it's still enabled in Atlassian
Actual Results
Because the user is completely managed by the IDP, the message
Go to your identity provider settings to manage how users log in with a second step
is shown instead. However, 2FA is enabled in Atlassian, and not in the IDP
Workaround
The org admin can manipulate admin.atlassian.com, calling the endpoint using the browser's developer console:
fetch('https://admin.atlassian.com/gateway/api/adminhub/organization/<org-id>/members/<AAid of the affected user>/mfa', { method: 'DELETE', credentials: 'same-origin', headers: {'Content-Type': 'application/json' } } ).then(console.log)
- is duplicated by
-
ACCESS-1128 When an Atlassian account is synced via provisioning or enforced MFA/2FA is configured, the "Deactivate two-factor authentication" button disappears
-
- Closed
-
- relates to
-
ACCESS-1209 Organization Admins Cannot Review or Disable 2-Step Verification on Managed Users
-
- Closed
-