You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.