Changing Group Name casing in AD, does not reflect in Crowd

Issue Summary

When group name casing is changed in AD, it does not reflect in Crowd and the following WARN is found in the logs.

2019-04-08 21:40:08,023 Caesium-2-2 WARN [directory.synchronisation.cache.DefaultGroupActionStrategy] remote group name [ GroupONe ] casing differs from local group name [ Groupone ]. Group details will be kept updated, but the group name cannot be updated

Steps to Reproduce

1. Create an AD External User Directory in Crowd of type connector and then synchronize to Crowd.
2. Check that all the groups in AD are synchronized.
3. In AD, change the casing of one of the groups for example from Group One to Group one
4. In Crowd, synchronize the AD External Directory

Expected Results

The group Group One is renamed to Group one

Actual Results

The group is not renamed and the following is found in the logs:

2019-04-08 21:40:08,023 Caesium-2-2 WARN [directory.synchronisation.cache.DefaultGroupActionStrategy] remote group name [ Group one ] casing differs from local group name [ Group One ]. Group details will be kept updated, but the group name cannot be updated

Workaround

One work around is as follows.

1. In AD, totally rename the group to a different name for example Group One to Groupone
2. Synchronise to Crowd, this will rename the group in Crowd to the new name
3. Now, in AD rename the group to the original name but with the new casing.