Summary

If 'Synchronize user details' is disabled on a delegated directory, and a user is renamed in that remote directory, then Crowd will create a duplicate user, despite the external ID being the same.

Steps to Replicate

1. Set up a delegated directory in Crowd
2. Uncheck 'Synchronize user details'
3. Set a 'User unique identifier attribute' in Crowd to be a unique field other than the user ID
4. Create a user on the remote directory, i.e. test_user.
5. Log in to a connected application (Jira/Confluence, etc)
6. In the remote directory, re-name the user to test_user2
7. Log in to a connected application with the updated user

Expected Behavior

Because the user has an external ID, Crowd should use this to validate that the user already exists, and has just been renamed

Observed Behavior

Crowd ignores the unique identifier, and creates a new user. The UI will now show the same user twice (old username and new username), and there will be 2 entries in the database.

Observed Behavior when synchronizing to other Applications

• In Confluence: After a sync, the user test_user and test_user2 will appear alternately in the User list