Unable to login with recovery_admin in Jira when Jira connected with Crowd and Confluence

[Muraleetharan Ramaraj]

Hi,

I want to reset Jira-System-Administrator password or create a new Jira-System-Administrator account. I tried the below steps to login recovery_admin as user name and Jira123 as password in Jira, but login failed with "username and password are not correct". The below approach works fine when Jira installed alone.

Login is failing when Jira is connected with Crowd and Confluence. My Jira version is Jira v8.0.2

1. Stop Jira with stop-jira.sh

2. Edit JVM_SUPPORT_RECOMMENDED_ARGS="-Datlassian.recovery.password=Jira123"

3. Start Jira with start-jira.sh

Can you please help me?

[Pavel Junek · Accepted solution]

Hi @Muraleetharan Ramaraj,

I think you will need to temporarily disconnect with Crowd to reset the password in Jira. It should be enough to change only the file JIRA/atlassian-jira/WEB-INF/classes/seraph-config.xml. 

The full description of the settings can be found at Integrating Crowd with Atlassian Jira 

Pavel

[Muraleetharan Ramaraj]

Hi Pavel,

Excellent! Finally I have successfully update the Jira System Administrator password.

Thank you so much for your help!

[Pavel Junek]

Your welcome :-)

Can you please mark the answer as Accepted? It will help others to find out that this issue is resolved.

Thank you

Pavel

[Lothilius]

@Pavel Junek  When you say "disconnect with Crowd" What do you mean exactly?

I have edited the seraph-config.xml file a few ways with no luck.

I'm running in to this same error after attempting to restore a backup from the cloud to a server "on prem" (AWS). 

[Pavel Junek]

Hi @Lothilius,

In your case, it will be another Use Case.

Here the solution is when using Atlassian Crowd app (for Server User Management), Jira and Confluence on the server version.

In your case, please use the instructions on Migrating from Jira Cloud to Server applications 

After the migration

5. Change the admin password

1. Log in to your new Jira application, using the following credentials: 
   
   • Username: sysadmin
   • Password: sysadmin

[Lothilius]

@Pavel Junek Thank you for the clarification. The problem is that we did try sysadmin first as specified in the documentation but that did not work, so we pivoted to try and see if the recovery process would work and neither seem to work.