When sAMAccountName casing does not match cn (User Logon Name (pre-Windows 2000) does not match User Logon Name), or casing of a user or group name has changed from original casing, synchs fail and access is affected

Synchronisations in Confluence fail when sAMAccountName and User Logon Name casing does not match (in Active Directory), or where the case has been changed after an initial synchronisation to Confluence.

We have a ticket where the casing does not match, or may have been changed from the initial casing in one field and not the other, which causes every second synch to fail, and removes the affected user's group memberships. Every subsequent synch is successful and restores group memberships.

This occurs up to version 4.2.11 of Confluence (the current version).

Resolution

• For users - fix the casing in AD so that the User Logon Name (pre-Windows 2000) matches the User Logon Name, and matches what is in Confluence, and synchronise again.
• For groups - fix the casing in AD so that the Group Name matches what is in Confluence, and synchronise again.