Confluence 3.5.13 LDAP Migration from Confluence 3.4.9

Question

In confluence 3.4.9, we use atlassian-user.xml for LDAP configuration. We upgraded our test instance to 3.5.13 and copied the atlassian-user.xm from old Confluence installation to new Confluence installation.

After upgrade, there is a directory named "Upgraded atlassian-user LDAP (ldapRepository)" under "User Directories" in confluence. There is no option to edit this directory from confluence UI.

I can see all LDAP groups under "Manage Groups", but there is no user group membership. I get "No users found" when i select the group in confluence.

Is there any other configuration which need to be done?

William Schneider · Answer

Though probably a best practice not to edit the directory you are logged in as, you can still edit the directory you are logged in under if you know the URL to use. On the /plugins/servlet/embedded-crowd/directories/list page, find the "synchronize" link for the LDAP repo and copy the xsrfTokenValue key and directoryId , and substitute them into the URL below: http://example.confluence.com/plugins/servlet/embedded-crowd/configure/ldap/?xsrfTokenName=atl_token&xsrfTokenValue=&directoryId= Again, probably not best practices, but I've done it several times without issue. Best of luck!

Alex Holtz · Answer

Vikas, you can't edit the User Directory that you're currently logged in with. If you don't already have one, create a new "confluence_admin" user in the internal confluence user directory -- don't forget to assign admin permissions -- and then login as that user; now you should be able to tweak the "upgraded atlassian-user..." user directory.

If you use local groups in Confluence you'll have to rebuild your groups because the user directory does not contain your group membership information, those groups are left behind in the "internal directory". You may wish to take this as an opportunity to evaluate the pros/cons of moving your groups into LDAP rather than managing them locally in Confluence.

However, I suggest creating a whole new "<myldap_name> Directory" because the migrated version doesn't always make the best choices for some of the settings.

Disable the existing "upgraded..." user directory and then create your new user directory. Once the sync is complete you can begin repopulating groups, either locally or in LDAP.

This topic is related and may be worth a read: https://answers.atlassian.com/questions/15329/jira-4-3-ldap-migration-from-jira-4-1-1

As always perform these changes in a test environment first!