You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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,
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 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.
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".