LDAP errors in log files

Jira is loggin below errors in atlassian-jira.log file however users are able to login and newly created users are also reflected in Jira.

2014-07-23 09:38:40,885 /servicedesk/customer/portal/7/create/127 [commons.ivm.routines.LDAPUserRoutine] LDAPUserRecord: NO LDAP QUERY ?

2014-07-23 09:38:41,025 /servicedesk/customer/portal/7/create/127 [commons.ivm.routines.LDAPUserRoutine] Cannot access LDAP. Please review the configuration.

javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C0903A9, comment: AcceptSecurityContext error, data 52e, v1db1]

2 answers

1 accepted

0 votes
Accepted answer

It was wrong configuration of LDAP in kepler addon.

The LDAP error code 49 means invalid credentials, specifically in this case the code 52e as you can see here.

Possibly there's some cache involved to the users still be able to log in. In any case, it's best to double check the username and password of the user you are using to connect to your LDAP.


I have cleared the cache and tried to login. It allows to login and whenever I perform any event on ticket, this error pops up.

This is happening only to one project of jira


thought of sharing attached logs

also it is able to synechronize sucessfully.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

879 views 3 9
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you