-
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
Resolution | New: Low Engagement [ 10300 ] | |
Status | Original: Long Term Backlog [ 12073 ] | New: Closed [ 6 ] |
Labels | Original: crowd-triage-support | New: cleanup-seos-fy25 crowd-triage-support |
UIS | Original: 6 | New: 5 |
UIS | Original: 5 | New: 6 |
UIS | Original: 0 | New: 5 |
UIS | Original: 5 | New: 0 |
UIS | Original: 6 | New: 5 |
UIS | Original: 1 | New: 6 |
UIS | Original: 0 | New: 1 |
UIS | Original: 1 | New: 0 |