LDAP Error Code 32

Symptoms

Users are unable to log in. The following appears in the atlassian-stash.log:

javax.naming.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-0310020A, problem 2001 (NO_OBJECT), data 0, best match of: 'ou=fake, ou=users, o=sevenSeas']; remaining name 'ou=users, o=sevenSeas'

Causes

There could be many reasons for this issue. Please check the data code (in the example above, it's 0) and match it with the description in the following table:

Data Code

Description

0 Defined DN does not exist

In the example above, ou=fake, ou=user, o=sevenSeas does not exist, but ou=users, o=sevenSeas does.

Resolution

Double check the Fully Qualified Domain Name on the LDAP side, including the prefixes (cn, ou, etc.), and ensure that it matches your directory configuration within JIRA.

(info) Please see our Troubleshooting LDAP User Management documentation for further assistance with diagnosing LDAP problems.

Last modified on Feb 26, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.