Deleting 'hidden' duplicated accounts
Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
As of release 8.19.0, the Jira platform REST API api/2/user
resource provides additional count
and list
methods that you can use to get the total number of duplicate user accounts or the full list of such accounts.
An account is considered as duplicate if another active account with the same name exists in another user directory, or if a user has multiple accounts and their only active account is not in the directory with the highest priority.
Environment
Jira version >= 8.19.0
.
Solution
Review the list of users from below rest api call.
Rest API
curl -X GET "<BASE_URL>/rest/api/2/user/duplicated/list" \
-u "<USERNAME>:<PASSWORD>"
The users from the above output, if they are from a directory lower in order are not visible in the UI.
Make sure that these users are no longer required to login to Jira.
After confirmation the below steps can be followed to remove them.
Plan for Jira downtime. (While Jira will not actually go down, the following steps will briefly change the user directory order, which may cause temporary login and permission problems for those users with duplicate accounts - see Managing multiple directories for further details on the impact of changing the user directory order.)
Move the Internal directory to the top in the order.
This would make the duplicate account from the Internal directory visible in the UI.
Delete these accounts and revert the directory order as earlier.
⚠️ Jira does not need to be restarted with this approach.
Was this helpful?