-
Bug
-
Resolution: Fixed
-
High
-
2.1
-
None
-
None
If you change the username of an LDAP/AD user and re-sync the cache the new username is not picked up.
One needs to disable/enable caching or change the username in the databse.
- incorporates
-
CWD-2421 'Lower Case Output' option can cause mismatch in database with applications
-
- Closed
-
- is related to
-
CONFSERVER-22515 After change an username in Active Directory and resynchronize, there are two accounts showing in Confluence (the old and the new username).
-
- Closed
-
- mentioned in
-
Wiki Page Failed to load
Actually, since Crowd can be configured to conditionally lower case the output, we need to cater for this case.
So if a user/group is returned from the server (Crowd or LDAP) in a different case than to what is stored in the DB (during sync), we should do a case-insensitive comparison on the name and log case miss-matches are ERRORs in the log. We will not attempt to rename the user as other apps, such as JIRA, use the username as a foreign key in application data.