We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-3227

Merge memberships for groups with duplicate names during LDAP directory sync

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • None
    • 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.

      Currently, if there is a duplicate group name in an LDAP directory, the duplicate group is dropped to allow synchronisation to continue. This was implemented in CWD-2504.

      It would be ideal if the memberships of these two groups could be combined. Users will not necessarily be aware that the duplicate group was dropped but may realize they are missing memberships for expected groups. The following is logged in atlassian-confluence.log:

      WARN [scheduler_Worker-1] [directory.ldap.cache.AbstractCacheRefresher] filterOutDuplicateGroups group[<groupname>] duplicated in remote directory. Ignoring group.
      

      Please see the discussion in the linked CONF-23213

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Crowd Data Center'
            1. Crowd Data Center
            2. CWD-3227

            Merge memberships for groups with duplicate names during LDAP directory sync

              • Icon: Suggestion Suggestion
              • Resolution: Won't Fix
              • None
              • None
              • None
              • 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.

                Currently, if there is a duplicate group name in an LDAP directory, the duplicate group is dropped to allow synchronisation to continue. This was implemented in CWD-2504.

                It would be ideal if the memberships of these two groups could be combined. Users will not necessarily be aware that the duplicate group was dropped but may realize they are missing memberships for expected groups. The following is logged in atlassian-confluence.log:

                WARN [scheduler_Worker-1] [directory.ldap.cache.AbstractCacheRefresher] filterOutDuplicateGroups group[<groupname>] duplicated in remote directory. Ignoring group.
                

                Please see the discussion in the linked CONF-23213

                        Unassigned Unassigned
                        dunterwurzacher Denise Unterwurzacher [Atlassian] (Inactive)
                        Votes:
                        4 Vote for this issue
                        Watchers:
                        6 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            dunterwurzacher Denise Unterwurzacher [Atlassian] (Inactive)
                            Votes:
                            4 Vote for this issue
                            Watchers:
                            6 Start watching this issue

                              Created:
                              Updated:
                              Resolved: