Issue Summary

User deletion from Crowd end does not remove the entries from User_mapping table in Confluence. However, the data is deleted from cwd_user table and user in not shown in Users in Confluence UI

Steps to Reproduce

1. Create a Crowd user directory (RW or Readonly) and connect with Confluence
2. Create a user in Crowd and synch it with Confluence. The user will be created in Confluence and data will be populated in cwd_user and user_mapping table along with other tables.
3. Delete the user from Crowd and synchronise. The user will be deleted from Crowd, Confluence , cwd_user table but the data(username and lower_username) will remain as the username. When we delete an internal user, the value of username and lower_username changes to user-key for that particular user.
4. When I deleted the user in Crowd, the user_mapping table looks like below

Expected Results

When user is deleted, the value of username and lower_username should change to user-key for that particular user. The behaviour of user deletion should be same for local user and crowd user in Confluence.

Actual Results

The user will be deleted from Crowd, Confluence , cwd_user table but the data(username and lower_username) will remain as the username. Due to this issue, when a customer creates a user with same username in Crowd (after the older one was deleted), since the username and lowerusername values still exists in Confluence for the old user, the content of old user will be shown in the activity/history for the new user which is seen as a security flaw by mu customer. Let's say the old user had name as Mark Elford and username marke and new user has name Mark Entinckap and same username marke, the content history of Mark Elford will be shown for Mark Entinckap

Workaround

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