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: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-8902

Renamed LDAP User Groups do not propagate to Global Permissions

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Low Low
    • None
    • 4.6.1
    • None
    • None

      Currently when an LDAP sourced user group is renamed and the user directory is synchronized, the updated group name is picked up as part of the user accounts, however the corresponding group name in Global Permissions is not updated as well.

      Steps to reproduce:
      1. Connect Bitbucket Server to and LDAP user directory
      2. Synchronize accounts within a user group.
      3. Grant the group Bitbucket User permissons in Administration >> Global Permissions.
      4. Rename the user group in LDAP.
      5. Re-synchronize the LDAP directory.
      6. Verify that the name of the group the users belong to was updated Administration >> Groups.
      7. Check Administration >> Global Permissions and see the original group name is still listed, and the new group name is not listed.
      Workaround:

      Manually add the new group name to Administration >> Global Permissions

            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: 'Bitbucket Data Center'
            1. Bitbucket Data Center
            2. BSERV-8902

            Renamed LDAP User Groups do not propagate to Global Permissions

              • Icon: Bug Bug
              • Resolution: Won't Fix
              • Icon: Low Low
              • None
              • 4.6.1
              • None
              • None

                Currently when an LDAP sourced user group is renamed and the user directory is synchronized, the updated group name is picked up as part of the user accounts, however the corresponding group name in Global Permissions is not updated as well.

                Steps to reproduce:
                1. Connect Bitbucket Server to and LDAP user directory
                2. Synchronize accounts within a user group.
                3. Grant the group Bitbucket User permissons in Administration >> Global Permissions.
                4. Rename the user group in LDAP.
                5. Re-synchronize the LDAP directory.
                6. Verify that the name of the group the users belong to was updated Administration >> Groups.
                7. Check Administration >> Global Permissions and see the original group name is still listed, and the new group name is not listed.
                Workaround:

                Manually add the new group name to Administration >> Global Permissions

                        Unassigned Unassigned
                        abromberg Aaron Bromberg (Inactive)
                        Votes:
                        1 Vote for this issue
                        Watchers:
                        7 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            abromberg Aaron Bromberg (Inactive)
                            Affected customers:
                            1 This affects my team
                            Watchers:
                            7 Start watching this issue

                              Created:
                              Updated:
                              Resolved: