-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
High
-
None
-
4
-
Severity 3 - Minor
Issue Summary
Atlassian Accounts that are managed no longer appear when searching for them in the managed accounts view.
In addition, the accounts can't be assigned to an authentication policy.
The actual state of the accounts in the system responsible for maintaining the data is accurate, but the system used for representing the state in admin UIs has gotten out of sync.
Steps to Reproduce
- Go to the admin HUB > Domain configuration page
- Check if there are any claimable Atlassian Accounts under the domain that is set to automatically claim accounts
- Export the accounts and extract the Atlassian Accounts that are not claimed.
- Claim the accounts
Expected Results
Accounts should be claimed successfully.
Actual Results
The account can't be claimed.
For the account affected :
- Their managed account profile is not returned when searching for their email address in Managed Accounts, but their profile is accessible by manually building the URL:
https://admin.atlassian.com/o/<Org_ID>/members/<Atlassian Account ID> - Org Admins can't assign an Authentication Policy.
Workaround
- For provisioned accounts, deleting their SCIM records by Atlassian Support or using the Deactivate a User instruction followed by re-provisioning the accounts, including the group memberships, solves the issue.
- Unclaim and reclaim the accounts.
- is related to
-
ACCESS-1715 Managed Atlassian Accounts no longer fully managed
-
- Closed
-
-
ACCESS-1920 Claimed account not fully managed
-
- Closed
-