-
Bug
-
Resolution: Fixed
-
Low
-
2.8.3, 2.8.4
-
None
-
None
-
Severity 3 - Minor
-
Summary
Users that are expired in Active Directory are supposed to be removed from Crowd during the first sync after the expiration date.
Environment
Crowd 2.9.1
AD 2012 R2
Steps to Reproduce
Set up a Connector in Crowd to sync with AD.
Tick "Filter out expired users" in the Connector tab
Expected Results
Expired users removed when the Directory is synchronized.
Actual Results
User is still in Crowd after synchronizing
Notes
Please see screen shots:
Workaround
No workaround at present.
- causes
-
-
- Gathering Impact
-
- is a regression of
-
CWD-3789 Allow users from AD to be filtered on the accountExpires attribute
- Closed
- is related to
-
-
- Closed
-
- was cloned as
-
KRAK-240 Loading...
[CWD-4736] Expired Users from AD not removed in Crowd
| Remote Link | New: This issue links to "Page (Confluence)" [ 449664 ] |
| Epic Link | Original: CWD-4704 [ 600140 ] |
| Workflow | Original: Simplified Crowd Development Workflow v2 - restricted [ 1508471 ] | New: JAC Bug Workflow v3 [ 3365684 ] |
| Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
| Link | New: This issue causes CONFSERVER-54319 [ CONFSERVER-54319 ] |
| Remote Link | New: This issue links to "Page (Extranet)" [ 279738 ] |
| Remote Link | New: This issue links to "Page (Extranet)" [ 269474 ] |
Confirming it's happening in 2.11.0 (which makes sense since it's fixed in 2.12.0)
Any ETA on .12. release?
| Fix Version/s | New: 2.12.0 [ 66140 ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Verified [ 10005 ] | New: Closed [ 6 ] |
Does this remove the user from Crowd and all applications thus leaving an unknow user entry in issues that were created/updated/edited? If so, this seriously complicates my companies decision on upgrading as we need to meet certain audit requirements.