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

Getting error 32 during ldap authcication.

Test Remote Directory Connection

Use this form to test the connection to Microsoft Active Directory (Read Only) directory 'Active Directory server'.

For extended testing enter the credentials of a user in the remote directory.

  Test basic connection : Succeeded
  Test retrieve user : Failed
org.springframework.ldap.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-031001A8, problem 2001 (NO_OBJECT), data 0, best match of: '' ]; nested exception is javax.naming.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-031001A8, problem 2001 (NO_OBJECT), data 0, best match of: '' ]; remaining name '/'
For more information regarding LDAP error codes see Troubleshooting LDAP Error Codes.

6 answers

Hey Anku,

According with that error (code 32), the specified entry does not exist in the directory (DIT). 

Basically error 32 says you're trying to log in with an inexistent user, or with a user which is on some part of your LDAP tree which isn't covered by your Base DN.

Interesting. I got the exact same issue today while trying to add LDAP to JIRA / Confluence. Funny enough all the users are synchronized with groups and stuff. But the cannot login. Any updates from your side?

Hi Matthias any luck on your issues? 

Experiencing the same issue 

No, Still getting the same error message.

Hi Paulo,

Now I am getting below error message. Can you please help me out?

Test Remote Directory Connection 

Use this form to test the connection to Microsoft Active Directory (Read Only) directory 'Active Directory server'.

For extended testing enter the credentials of a user in the remote directory.

 Test basic connection : Succeeded
 Test retrieve user : Failed
org.springframework.ldap.PartialResultException: nested exception is javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: imfcorp.com:389 [Root exception is java.net.ConnectException: Connection refused]]
Thanks & Regards,
Anku Sharma 


Hi Paulo,

Thanks for your support. I am successfully able to authenticate with AD now.

 

Regards,

 Anku Sharma


Hi Anku,

We are facing the very same error message on testing retrieve user . Can you share how you resolved that issue?

 

Thanks,

Anubha

 

We had the same issue. After investigation, JIRA uses an Active Directory (AD) user to login to the LDAP directory.

We were using this AD user for other purposes than connecting to JIRA and for some reason, this account was locked by the network security rules.

Unlocking the AD account resolved the issue.

Hope this help.

Suggest an answer

Log in or Sign up to answer
TAGS

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