Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-23213

Merge memberships for groups with duplicate names during LDAP directory sync

    XMLWordPrintable

Details

    • 21

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.

      Whatever the administrator enters in as the "Group name attribute" must be unique for all groups in the LDAP server. Typically this is the "CN" attribute.

      In the event that two different entities in LDAP are found with the same value for that attribute (CN), you receive the following stack trace.

      2011-09-01 00:26:43,979 ERROR [QuartzScheduler_Worker-2] [atlassian.crowd.directory.DbCachingDirectoryPoller] pollChanges Error occurred while refreshing the cache for directory [ 142802946 ].
java.lang.IllegalArgumentException: duplicate key: duplicatedGroupName
at com.google.common.collect.RegularImmutableMap.<init>(RegularImmutableMap.java:62)
at com.google.common.collect.ImmutableMap$Builder.fromEntryList(ImmutableMap.java:210)
at com.google.common.collect.ImmutableMap$Builder.build(ImmutableMap.java:196)
at com.google.common.collect.Maps.uniqueIndex(Maps.java:456)
at com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher.synchroniseMemberships(AbstractCacheRefresher.java:126)

      Excluding these duplicates from the sync is not possible due to the fact that we can't control the order in which groups are returned from the LDAP server. If the ordering were to change between syncs, the memberships could keep changing on the Confluence side.

      The solution to this problem is to amalgamate memberships for groups which share the same name on the remote server. We should make this an option in the LDAP configuration.

      Attachments

        Issue Links

          is blocked by

          Suggestion - CWD-3227 Merge memberships for groups with duplicate names during LDAP directory sync

          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. CWD-2681 Crowd 2.3.3 does not sync user memberships when multiple LDAP groups have the same name

          • Highest - Our top priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. CWD-2504 Synchronization with JIRA/Confluence fail with duplicate entry

          • Medium - Medium priority issues
          • Closed

          Suggestion - CWD-2441 Use sAMAccountName attribute for group name by default when using Active Directory

          • Closed

          Suggestion - CONFSERVER-23213 Merge memberships for groups with duplicate names during LDAP directory sync

          • Gathering Interest

          Activity

            People

              Unassigned Unassigned
              twong Tim Wong (Inactive)
              Votes:
              41 Vote for this issue
              Watchers:
              42 Start watching this issue

              Dates

                Created:
                Updated: