Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Resetting JIRA Administrator password haven't worked

Kevin Kirchhof April 28, 2018

Hello everyone,

After Installation of Crowd, I was not able to Login to JIRA anymore. So this time I've resetted the JIRA Password like described in for my JIRA instance Version 7.x, running on dedicated mySQL Server, with the administrator username.
But resetting the username via SQL haven't worked für me. I am still not able to Login to JIRA, even though I have Crowd nit running, resetted the Password, started JIRA instance.

Can someone please help why (a) Crowd does not enable me to Login to JIRA and (b) why JIRA's internal user-Directory does not accept the recently resettet Password for the administrator user?

Thank you very much in advance,


1 answer

1 accepted

0 votes
Answer accepted
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 30, 2018

Hi Kevin,

If the Jira instance has been set up for single sign-on through Crowd, the internal Jira directory will not authenticate users. Please see Integrating Crowd with Atlassian JIRA. Make sure the default authenticator is enabled and the SSO connector is commented out in the JIRA/atlassian-jira/WEB-INF/classes/seraph-config.xml file. Comment out the custom authenticator node, comment in the default authenticator, reversing Step 2. Configuring JIRA to talk to Crowd Comment out the authenticator node and comment in the default authentication as Jira had out of he box.

Also, backup/rename the crowd.properites from JIRA/atlassian-jira/WEB-INF/classes/seraph-config.xml file.

Please make sure your admin user has the active field set to true in the cwd_user table in the database.



Kevin Kirchhof May 1, 2018

Hi Ann, 

thanks for the reply. Sadly since there is Crowd installed, none of mine Atlassian application work anymore - at least the login to them. I had the workarouund that, as long Crowd was stopped, the applications used their internal directories to authenticate via the "old" users stored in them correctly. But now even this is not working anymore. I will try to configure JIRA backwards to use it's internal directory an check how it will work.

Updates coming soon. 



Kevin Kirchhof May 14, 2018

Hi @AnnWorley,

I guess I found out the problem: it was a missconfiguration of my proxy settings of Crowd. So the authentication requests against Crowd were redirected to a wrong desitnation.

Now, having Crowd without any proxy configuration, the server runs well and authenticates the user properly against Crowd.

Unfourtunatly I am still not able to login to Jira, but it seems as if there are the same problems in configuration of the Jira application proxy settings and the configuration of Crowds "accepted proxies".

Kevin Kirchhof May 19, 2018

I see this question as solved, cause I guess the problem relates to the fact, that I've set up Jira to use SSO (Crowd) to authenticate, so the values set in Jira's database were never touched and so won't work.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events