-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
None
-
5
-
Severity 3 - Minor
-
5
-
When a user connected by LDAP is removed from LDAP, the cwd_user record is removed, but the corresponding cwd_membership record will remain as an orphaned record.
Steps to reproduce
- Link Crowd to an LDAP Directory
- Synchronize so a user (with a group membership) is added to Crowd
- Search the database for the user in the cwd_user table and cwd_membership table (should exist in both)
- Remove the user from the LDAP
- Synchronize with Crowd
- Search the database for the user in the cwd_user table and cwd_membership table
Expected Result
User is removed from both tables
Actual Result
The user record will exist in cwd_membership but not in cwd_user
Other Information
This can create an issue in a database audit situation where records do not match across tables
- is related to
-
CWD-4801 Provide a feature for Crowd to always re-evaluate group memberships in Active Directory with Incremental Sync
- Closed
[CWD-4867] When connected to LDAP and a user is removed, their corresponding record is not removed from cwd_membership
We've had a similar situation in AD (user had 2 accounts, one was removed) that did not seem to cause Crowd to fail (running 2.11.1 now) - it did trigger SSP-20741 in Bitbucket though which seems to be the same root cause.
atlassianadmins.au Crowd 2.11.0 fixes the observed cases of this for incremental synchronisation as a part of https://jira.atlassian.com/browse/CWD-4801.
Could you please verify that you still encounter the issue with the latest version? Thanks!
More critically (as per CWDSUP-13545) if the user then does need to come back in, it breaks the sync due to the constraint on the cwd_membership table as it's trying to insert a duplicated entry
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Crowd Data Center, please check our public roadmap.
Kind regards,
Crowd Data Center