How to ensure JIRA keeps working if you change your Active Directory domain
Platform Notice: Data Center Only - This article only applies to Atlassian products 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
Sometimes you may need to change your Active Directory domain. This may affect JIRA if you have it connected to your Active Directory for user synchronisation and/or authentication. Due to the domain change you may find that one of the following is changed:
Base DN
User DN
This procedure will ensure you have the minimum downtime for your users while such a change is made.
Solution
Resolution
Before making any change in Active Directory, make sure the following is true in JIRA:
There is a JIRA Internal Directory and it is enabled
At least one user exists in that directory who is an administrator
Confim that you are able to log in as that user
Immediately after making the change in Active Directory:
Log in as the internal directory administrator user confirmed in the above steps
Edit the Active Directory user directory, updating the Base DN and User DN as needed
Confirm this directory can synchronise
Confirm a user from that directory can log in to JIRA
ℹ️ See Configuring User Directories for details on how to configure user directories in JIRA.
Was this helpful?