Jira fails to authenticate users including jira-admin

[Michael Dowling]

We are using Jira 4.2.2 with crowd. Crowd uses a filter when connecting to our Active Directory server. I had modified that AD filter to include some people that were excluded from the original one. I tried to check with Jira that these users were indeed now included when I was prompted for the jira-admin password. It failed to authenticate jira-admin. Other users were nevertheless still able to be authenticated.

A little later, Jira still failed to authenticate jira-admin, but instead of blankly refusing access, it asked for a capcha. And it keeps asking for a capcha, and access is never achieved. And then the other users were also being refused access, and Jira is currently unusable.

[Michael Dowling]

It wasn't a Jira problem but a crowd one; synchronise against AD and Jira (eventually) authenticates.

This solves the problem.

[Tiago Comasseto]

Hello there,

It is a bit dificult to be sure at this point, but I have some questions that may help you to identify what is the root cause.

• After modify the filter, is the directory synchronizing correctly in Crowd?
• Was this the only modification?
• Does the login test work for those users in Crowd? (See this page: https://confluence.atlassian.com/display/CROWD/Testing+a+User%27s+Login+to+an+Application)
• If you rollback the filter and restart JIRA (to refreash the cache), are the users able to authenticate again?

I hope this information has helped, but if you are still facing problems, please open a support request at href="https://support.atlassian.com">https://support.atlassian.com and attach both Crowd and JIRA logs:

• https://confluence.atlassian.com/pages/viewpage.action?pageId=231932826
• https://confluence.atlassian.com/display/CROWD/Logging+and+Profiling

Cheers,

Tiago Comasseto