LDAP quick connects but fails on AD search

Brad Pink January 7, 2014

Attempting to connect to Microsoft Active Directory.

Initial (quick) test returns: "Connection test successful."

Search of AD returns:

"Test retrieve user : Failed

org.springframework.ldap.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-031001E5, problem 2001 (NO_OBJECT), data 0, best match of: '' ]; nested exception is javax.naming.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-031001E5, problem 2001 (NO_OBJECT), data 0, best match of: '' ]; remaining name '/'"
Config is as follows:
=== Current user ===
Directory ID: 1
Username: ########
Display name: #############
Email address: ########@#######.org.au
=== Directories configured ===
Directory ID: 10000
Name: Active Directory server
Active: true
Type: CONNECTOR
Created date: Wed Jan 08 15:19:47 CST 2014
Updated date: Wed Jan 08 15:33:34 CST 2014
Allowed operations: [CREATE_GROUP, DELETE_GROUP, UPDATE_GROUP, UPDATE_GROUP_ATTRIBUTE, UPDATE_USER_ATTRIBUTE]
Implementation class: com.atlassian.crowd.directory.MicrosoftActiveDirectory
Encryption type: sha
Attributes:
"autoAddGroups": "jira-users"
"com.atlassian.crowd.directory.sync.currentstartsynctime": "null"
"com.atlassian.crowd.directory.sync.issynchronising": "false"
"com.atlassian.crowd.directory.sync.lastdurationms": "63"
"com.atlassian.crowd.directory.sync.laststartsynctime": "1389157414304"
"crowd.sync.incremental.enabled": "true"
"directory.cache.synchronise.interval": "3600"
"ldap.basedn": "#######.local"
"ldap.connection.timeout": "10000"
"ldap.external.id": "objectGUID"
"ldap.group.description": "description"
"ldap.group.dn": "###### groups"
"ldap.group.filter": "(objectCategory=Group)"
"ldap.group.name": "cn"
"ldap.group.objectclass": "group"
"ldap.group.usernames": "member"
"ldap.local.groups": "true"
"ldap.nestedgroups.disabled": "true"
"ldap.pagedresults": "true"
"ldap.pagedresults.size": "1000"
"ldap.password": ********
"ldap.pool.initsize": "null"
"ldap.pool.maxsize": "null"
"ldap.pool.prefsize": "null"
"ldap.pool.timeout": "0"
"ldap.propogate.changes": "false"
"ldap.read.timeout": "120000"
"ldap.referral": "true"
"ldap.relaxed.dn.standardisation": "true"
"ldap.roles.disabled": "true"
"ldap.search.timelimit": "60000"
"ldap.secure": "false"
"ldap.url": "ldap://########:389"
"ldap.user.displayname": "displayName"
"ldap.user.dn": "###### users"
"ldap.user.email": "mail"
"ldap.user.encryption": "sha"
"ldap.user.filter": "(&(objectCategory=Person)(sAMAccountName=*))"
"ldap.user.firstname": "givenName"
"ldap.user.group": "memberOf"
"ldap.user.lastname": "sn"
"ldap.user.objectclass": "user"
"ldap.user.password": "unicodePwd"
"ldap.user.username": "sAMAccountName"
"ldap.user.username.rdn": "cn"
"ldap.userdn": "JIRA_USER@######.local"
"ldap.usermembership.use": "false"
"ldap.usermembership.use.for.groups": "false"
"localUserStatusEnabled": "false"
Directory ID: 1
Name: JIRA Internal Directory
Active: true
Type: INTERNAL
Created date: Thu Feb 28 11:57:51 CST 2013
Updated date: Thu Feb 28 11:57:51 CST 2013
Allowed operations: [CREATE_GROUP, CREATE_ROLE, CREATE_USER, DELETE_GROUP, DELETE_ROLE, DELETE_USER, UPDATE_GROUP, UPDATE_GROUP_ATTRIBUTE, UPDATE_ROLE, UPDATE_ROLE_ATTRIBUTE, UPDATE_USER, UPDATE_USER_ATTRIBUTE]
Implementation class: com.atlassian.crowd.directory.InternalDirectory
Encryption type: atlassian-security
Attributes:
"user_encryption_method": "atlassian-security"

3 answers

1 vote
BernardoA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 27, 2014

Maybe some 'CN' does not exist or no longer exists when it periodically attempts to synchronize with the Directory.

1 vote
Septa Cahyadiputra
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 7, 2014

Hi Brad,

It seems there is a misconfigureation on your end. According to your error, you are currently encountering a known issue which is describe in detail here:

https://confluence.atlassian.com/display/CONFKB/LDAP+Error+Code+32

Please refer the above KB and see if it helps.

Cheers,
Septa Cahyadiputra

0 votes
Timo Riikonen December 21, 2016

Basically 32 says that your query results with zero lines.

Note that the query is assembled from three settings:Base DN, Additional User DN and User Object Filter.

In my case I tried to use conflicting settings on the last two as I had forgotten the third setting.

 

Suggest an answer

Log in or Sign up to answer