Issue Summary

Each application in Crowd has a 'Lower case output' setting that enables you to sync users/groups in all lowercase to the external application (e.g. Confluence).

If you have already synchronised groups to the external application, then you enable/disable the 'Lower case output' option in Crowd, existing groups that were synchronised do not get updated to the correct letter case.

This is reproducible on Data Center: Yes

Steps to Reproduce

1. Connect Crowd to an Active Directory and map it to an external application (Confluence). Make sure there are groups in AD with mixed case names (e.g. Confluence-Group).
2. For the application's settings, enable 'Lower case output'.
3. Perform a Crowd sync in Confluence.
4. You'll notice that groups are synchronised in all lowercase (e.g. confluence-group).
5. Add this group to Global Permissions, Space Permissions or Page Restrictions.
6. Head back to Crowd and disable the 'Lower case output' setting.
7. Sync the directory in Confluence.

Expected Results

The group names are updated to use the proper name from the source directory (e.g. Confluence-Group).

Actual Results

The group names remain in all lowercase (e.g. confluence-group).

If you recreate the Crowd directory to have the groups' names updated to mixed case, then pages where the group names were used like Space Permissions will now throw this warning:

confluence-group
Case incorrect. Correct case is: Confluence-Group

Workaround

Currently there is no known workaround for this behaviour. A workaround will be added here when available.