Unable to login JIRA after Restoring from Backup
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
Problem
After restoring JIRA into a new instance user is unable to login
The following appears in the atlassian-jira.log
1
2015-09-30 23:11:58,628 http-bio-8617-exec-20 ERROR anonymous 1389x36x1 - 127.0.0.1 /rest/gadget/1.0/login [crowd.manager.application.ApplicationServiceGeneric] Directory 'Delegated LDAP Authentication in BASF' is not functional during authentication of 'XXXXXX'. Skipped.
Cause
The JIRA Internal Directory's order is not configured as the first or on top. Therefore , JIRA is looking for the user from the external directory
Resolution
Manually manipulate the database to re-order JIRA internal directory to be on top by running this SQL Queries :
Run this query to check the correct Directory IDs
1select id,directory_name,directory_position from cwd_directory;If the JIRA Internal Directory's id is 1 ( default ) , run this query to change the directory_position to 0 ( first )
1update cwd_directory set directory_position=0 where id=1Check to see if there are any other directories using the directory_position=0
1select id,directory_name,directory_position from cwd_directory where directory_position=0;If there are, any other ID besides the JIRA Internal Directory having the directory_position= 0, then update it to another number using step 2 but replacing id=1 with the appropriate id.
Managing 500+ users across Atlassian products?
Find out how easy, scalable and effective it can be with Crowd!
See
.
Was this helpful?