Renaming of Active Directory groups is breaking permissions

[stefan_baader_cpp_canon]

We have (mostly yearly) the problem that organizational groups are renamed in Active Directory (department names are changing etc.) and the impact is that a lot of group names in Confluence also changes (= old groups are removed, new groups are created and memberships added). In all spaces where this groups are permitted the permissions are broken. How can this be avoided or worked around?

[Brant Schroeder · Accepted solution]

@stefan_baader_cpp_canon Welcome to community.  Confluence uses Crowd connector when connecting to LDAP.  The connector unfortunately does not support LDAP name changes.  There are requests for this functionality in Confluence, Jira and Crowd. 

• https://jira.atlassian.com/browse/CWD-4763
• https://jira.atlassian.com/browse/CONFSERVER-9159  

I believe that this work around will work.  I would suggest testing it in a development environment first.  https://confluence.atlassian.com/confkb/how-to-rename-a-group-and-preserve-its-permissions-948228977.html