-
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
Workaround
No workaround at present.
- causes
-
CONFSERVER-54319 Expired Users from AD not removed in Confluence
-
- Gathering Impact
-
- is a regression of
-
CWD-3789 Allow users from AD to be filtered on the accountExpires attribute
- Closed
- is related to
-
BSERV-9023 Expired user in Active Directory still being synced
-
- Closed
-
- was cloned as
-
KRAK-240 Loading...
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.