I have the following problem in our Crowd instance, where the users and groups come from Active Directory: If a group consisting at least one user gets removed in Active Directory, the group including its users still remain in Crowd, even if I manually synchronise the directory. The only workaround that seems to work is to disable and re-enable caching, such that effectively a full synchronization is performed.
Is the group deletion synchronization not supported, is it a bug or am I doing something wrong, e.g., misconfiguration?
Please note that we are currently running an old version of Crowd (2.12).
Given the age of that Crowd release, my first instinct would be to look at upgrading. The amount of effort involved in upgrading a Crowd instance is fairly minimal. There are only a few weeks left before 2.12 hits end-of-life as well.
I see you've opened a support case related to this issue. Once a resolution for this issue is available, I'll post it here for the benefit of others searching for this question.
I'm Alison Huselid, Head of Product for Data Center at Atlassian. As we shared in our last post, we’ve been working on a solution for those of you who work for charitable non-profit organizations tha...
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