[CWD-3190] Incremental Crowd/Crowd synchronisation produces inconsistent events when a membership is deleted and recreated

Type: Bug
Resolution: Low Engagement
Priority: Medium
Fix Version/s: None
Affects Version/s: None
Component/s: Directory - Remote Crowd
Labels:
- cleanup-seos-fy25

Support reference count:
2
Symptom Severity:
Severity 2 - Major
UIS:
0
Bug Fix Policy:
View Atlassian Server bug fix policy

When Crowd processes synchronisation events to send to clients it omits membership deletion events if that membership still exists (on the assumption that it's a shadowed membership change). However, if that membership is now present because it was recreated since the deletion then Crowd will still send the recreation event, which will now fail as that membership was never deleted.

Either the initial deletion should still be sent or the recreation should also be omitted.

Discovered while testing

CWD-3182 Should not fail to add a user membership to a group for a Directory if the membership already exists

Closed

mentioned in: Wiki Page Failed to load

No work has yet been logged on this issue.

Assignee:: Unassigned

Reporter:: joe

Affected customers:: 1 This affects my team

Watchers:: 4 Start watching this issue

Created:: 11/Mar/2013 12:49 AM

Updated:: 09/Apr/2025 5:26 PM

Resolved:: 09/Apr/2025 5:26 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates