-
Bug
-
Resolution: Fixed
-
Highest
-
3.5
-
None
A customer with a large number of users in LDAP in 3.4.x or below would need to set up 3.5+ without migrating the atlassian-user.xml file (as automatic migration for large LDAP instances is not supported), so that no LDAP directory is set up in 3.5+. This involves adding the LDAP directory again manually, but all group memberships between LDAP users and local groups or LDAP groups and local users are lost. Confluence doesn't currently support an easy migration of this configuration.
A manual migration process needs to be put in place that allows such users to migrate their memberships.
Solution
Follow the "Resolution" steps in the LDAP synchronisation process takes too long if number of users or groups is large KB article.
- causes
-
CONFSERVER-24759 It is not possible to migrate external users that are not members of an internal group
-
- Closed
-
- is duplicated by
-
CONFSERVER-22518 Allow migration to the Delegated LDAP directory during upgrade
- Closed
-
CONFSERVER-22592 script to migrate users from old user management tables to a DELEGATED directory
- Closed
- relates to
-
CONFSERVER-22709 Add on the fly group sync for delegated LDAP authentication.
- Closed
-
CONFSERVER-22297 Ability to Copy or Move Users/Groups from One User Directory to Another
- Gathering Interest
- mentioned in
-
Page Loading...
Hi Bryan,
Sorry about the confusion. I've updated the issue description to include the solution. Note that even though the article currently says to upgrade to "3.5.12 or later", Confluence 3.5.11 has the migration implemented as well. The only difference is Confluence 3.5.11 does not yet have the "Synchronise Group Memberships" option. It will be in 3.5.13 which will be released in 1-2 working days.
Regards,
Niraj.