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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello Atlassian Community,
I have some strange behaviors during login. The first time I try to login takes about 60s and usually fails. The second time I try logging in, it sometimes works. I know that my password is correct because I use a password manager and so it never changes each time I try to log in. It happens so much that I can tell within the first second. If the browser tab does not update with my site URL, then I can click Login again and repeat the process to log in successfully.
Here is the setup: I am using a LDAP Authentication with Microsoft Active Directory.
Here is the log line: 2020-02-25 17:27:45,504-0500 http-nio-80-exec-13 ERROR anonymous 1047x4176x1 9w0mt9 0:0:0:0:0:0:0:1 /rest/gadget/1.0/login [c.a.c.manager.application.ApplicationServiceGeneric] Directory 'HAM LDAP Authentication' is not functional during authentication of 'mtxxxxx'. Skipped.
the error message of LDAP
Directory 'HAM LDAP Authentication' is not functional during authentication of 'mtxxxxx'. Skipped.
might already point to the right direction. Although some special cases like an out-of-memory situation on the Jira server comes to mind I really would start with diagnostics on the directory server - and probably between the Jira server and the directory server.
At least the error message tells that there _is_ some kind of malfunction with LDAP/AD.
Unfortunately it is hard to tell where the culprit actually is. Having a deeper look into log files, and maybe, choosing a DEBUG error level could help.
Maybe some other members with AD authentication knowledge come up with further ideas.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.