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.
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.
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:
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs