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?
@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.
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
Did you know that penalties up to 4 % of the yearly company turnover are possible in case of GDPR violations? GDPR regulations are currently mainly relevant for companies in the EU, but countries lik...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events