LDAP error code 34 when adding multiple AD Ldap server

Service Desk November 6, 2017

hi all,

am attempting to add multiple AD Ldap servers for redundancy in confluence. Intended for read-only ldap authentication - don't need confluence to write back to AD

have three servers added with identical configuration settings.

First two servers sucessfully test and synchronise.

Third server returns following error:

[LDAP: error code 34 - 0000208F: NameErr: DSID-03100225, problem 2006 (BAD_NAME), data 8349, best match of: 'ou=people,ou=cusa,dc=cusa=dc=com,dc=au']

 

difficult to see this as a configuration error, since i have two identical (that i can tell) ldap servers that validate just fine. Have manually copy/pasted config from one server entry to another with no observable change.

 

1) Any idea where ldap logging is stored by confluence? (windows-based install)

2) confluence does support multiple LDAP connections to same AD?

3) any further tips on troubleshooting.

1 answer

0 votes
Lars Olav Velle
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.
November 7, 2017

1. Ldap logging would be in either atlassian-confluence.log or catalina.out

2. No, meaning you cannot add multiple servers into one user directory. 

We have the following setup which enables us to have load balancing and fault tolerance:

  • 2 frontend servers with one virtual IP (keepalived) The virtual IP is moved to the other server approx 1-2 seconds after one host is taken down. JIRA keeps talking to the virtual IP.
  • Haproxy which forwards the requests back to several AD servers.
  • SSL termination in haproxy

3. Do you have follow referrals enabled? Are you using SSL?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events