Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-13131

Sync group deletion when using delegated user directory

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Crowd
    • None
    • 3
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem Definition

      When using the delegated directory (internal directory with LDAP authentication) with Synchronise Group Memberships flag enabled, groups are created, if they do not exist, within the application when the user authenticates. On each authentication, their group memberships are synchronized.

      However, if the group that was created in the application is deleted from the LDAP or all the users are removed, the group remains within the application when using embedded Crowd..

      For enterprise customers, this can have adverse performance affects as the groups continue to grow but are never cleaned.

      Suggested Solution

      Embedded Crowd should detect if an LDAP group is deleted on syncs with directory membership and remove the group. Further, if embedded Crowd detects that all memberships of a group have been zeroed out, the group should be removed.

      The end goal is to clean deleted and disregarded groups so that they do not collect and cause performance issues in the application.

      Workaround

      Identify the groups that have been deleted or zeroed out and manually remove the group in the application.

            Unassigned Unassigned
            mwilliams@atlassian.com Mark A.
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: