Changing LDAP schema casts Confluence AD integration unoperable

Posted by Maxim V. Pavlov on Server Fault See other posts from Server Fault or by Maxim V. Pavlov
Published on 2013-10-08T08:11:31Z Indexed on 2013/10/21 15:57 UTC
Read the original article Hit count: 260

Filed under:
|
|

I have had our instance of Atlassian Confluence configured to be integrated with our Active Directory.

In AD, all the users were being created under default Users folder in Active Directory Users and Computers.

We have decided to introduce cleaner separation and have created an Organizational Units structure in AD. Under root we have created Managed OU, and under it - Users OU and all user accounts were moved under Users OU.

Now I though that to let the Confluence AD integration engine "know" where to look for user accounts now, I only need to adjust the BaseDN and prepand it with ou=Managed so it is aware that it is looking for cn=Users but under ou=Managed. That didn't work.

How should I adjust LDAP schema root in a client application for it to be able to look for users in OU that then in a default folder.

© Server Fault or respective owner

Related posts about active-directory

Related posts about ldap