LDAP - JIRA - You cannot move the directory without losing your system admin privileges.
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
Platform Notice: Server, Data Center, and Cloud By Request - This article was written for the Atlassian server and data center platforms but may also be useful for Atlassian Cloud customers. If completing instructions in this article would help you, please contact Atlassian Support and mention it.
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
Problem
After setting up the external directory-LDAP, user is unable to re-order the Directories with below error:
Cause
Current user has it's own username both on internal and LDAP, but current user is an administrator on JIRA internal directory, but it does not have administrator permission on LDAP.
Note that if the user name is only available on JIRA internal directory and not available in LDAP there won't be any issue as it checks the first Order(LDAP) and can't find the user name so it checks the second order(Internal Directory) and matches the credentials.
Resolution
One way to address this issue is to login as an admin user in the Jira Internal Directory to make this change. Otherwise, you can perform one of the following:
- Create an Administrator group on LDAP and give this group Administrator permission on the JIRA Global Permissions
or
- If user belongs to a group on LDAP you can grant that group administrator permission on JIRA