Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,296,443
Community Members
 
Community Events
165
Community Groups

Resetting JIRA Administrator password haven't worked

Edited

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 https://confluence.atlassian.com/jira/retrieving-the-jira-administrator-192836.html 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,

Kevin

1 answer

1 accepted

0 votes
Answer accepted
AnnWorley Atlassian Team Apr 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.

Thanks,

Ann

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. 

Thanks,

Kevin

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".

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
TAGS
Community showcase
Posted in Jira Service Management

Jira Service Management Documentation Opportunities

Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...

320 views 0 10
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you