Issue Summary

If a renamed user logs in before the next synchronisation, embedded Crowd will rename the user. However, it does not update Bamboo permission entries in the same way that a directory synchronisation does.

Since the user is renamed from a Crowd perspective, the next sync won't detect a rename and permissions won't be updated at that point either.

Steps to Reproduce

1. Connect Bamboo to Active Directory (AD) and sync
2. Add a specific AD user to have plan permissions
3. Rename the user in AD
4. Login as that user before the next syncronization

Expected Results

Permissions are preserved upon rename.

Actual Results

Permissions aren't preserved.

Workaround

1. Rename the user back to the pre-renamed username and perform a directory synchronisation at User directories >> Synchronise
2. Rename the user back to the desired target username and perform a directory synchronisation at User directories >> Synchronise before the user logs in for the first time after the rename