This page last changed on May 09, 2006 by david.soul@atlassian.com.

Confluence 2.1 carries a new User system - Atlassian User. It is compatible with most existing osuser.xml configurations, but if you are running with the OSUser LDAP integration, you will need to change one line of osuser.xml to get it to work with Confluence 2.1.

Please see the original instructions for setting up an osuser.xml which can integrate with LDAP.

You must ensure that the only CredentialsProvider in your osuser.xml is the ConfluenceLDAPCredentialsProvider (see below).

The one line change to osuser.xml

The LDAPCredentialsProvider class changes from

<provider class="com.opensymphony.user.provider.ldap.LDAPCredentialsProvider">

to

<provider class="com.atlassian.confluence.user.ConfluenceLDAPCredentialsProvider">

Thus, the final configuration for the credentials provider is:

<provider class="com.atlassian.confluence.user.ConfluenceLDAPCredentialsProvider">
<property name="java.naming.factory.initial">com.sun.jndi.ldap.LdapCtxFactory</property>
<property name="java.naming.provider.url">ldap://localhost:389</property>
<property name="searchBase">dc=atlassian,dc=com</property>
<property name="uidSearchName">cn</property>
<!--
<property name="java.naming.security.principal">cn=Manager,dc=atlassian,dc=com</property>
<property name="java.naming.security.credentials">secret</property>
<property name="exclusive-access">true</property>
-->
</provider>

With Confluence 2.2 this single line change seems to be not sufficient any longer. Confluence 2.2 will always check the password against the Confluence password not the LDAP password. What can I do to use traditional osuser.xml configuration with Confluence 2.2?

Posted by eckhardt_f at Apr 29, 2006 14:14

Yes, this is a known issue: http://jira.atlassian.com/browse/CONF-6052.

We have fixed this in Confluence 2.2.1. Thanks for letting us know.

Cheers,
Dave

Posted by dave@atlassian.com at May 03, 2006 21:56
Document generated by Confluence on Feb 07, 2007 23:55