Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Login success is hit or miss

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.

1 answer

0 votes
Daniel Ebers Community Leader Mar 16, 2020

Hi Todd,

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.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

194 views 6 7
Read article

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