Bitbucket Server Developer

Bitbucket Server Developer

Rate this page:

User Erasure Plugin Module


Plugins can implement a user erasure handler to participate in the user erasure process for a user. User erasure is used to remove personally identifiable user data, or replace it with an alias if the data can not be removed.

Difference between user erasure and user deletion

User deletion removes a user from Bitbucket, while user erasure modifies a deleted user by updating their personally identifiable information (i.e. replacing their username with a non-attributable alias).

When a user is deleted, data such as permissions, SSH keys and access tokens are deleted (once the UserCleanupEvent is published for that user some time after the actual deletion). When a user is erased, their username is changed to a non-attributable alias, their personal project key is renamed to this alias, and any mentions to their original username updated to this alias.

To erase a user, that user must be first deleted. The UserCleanupEvent is guaranteed to have run before a user is erased. If your plugin needs to perform some kind of cleanup on every deleted user (e.g. deleting user settings), you should listen to the UserCleanupEvent with an event listener. However, if your plugin persists personally identifiable user data (e.g. displays a username for user in the UI), you can implement a user erasure handler and update or remove that information.

How to use the UserErasureHandler

The UserErasureRequest parameter in UserErasureHandler#eraseUser(..) supplies an originalUsername and an updatedUser. If your plugin stores user data by username, you can use the originalUsername to look up the relevant data for the user being erased. If your plugin stores user data by user ID, you can use updatedUser.getId() to look up the relevant data. Since the user is deleted it won't be accessible through the Bitbucket user APIs (e.g. UserService and UserAdminService). Once you have this data, you can either delete it if appropriate, e.g. deleting avatars, or update it to use the new username for the user (updatedUser.getUsername()), e.g. user mentions.


The element for the user erasure plugin module is <user-erasure-handler/>. It allows the following configuration attributes:


keyYesThe identifier of the plugin module. This key must be unique within the plugin where it is defined.
classYes A user erasure handler definition containing a fully qualified class name. This class must implement UserErasureHandler.
weightThe (integer) weight of the plugin module. User erasure handlers with a higher weight will be processed later. Third party plugins must use a weight greater than 100


Here is an example for a custom user erasure handler:

<atlassian-plugin key="${project.groupId}.${project.artifactId}" name="${}" plugins-version="2">
        <vendor name="${}" url="${project.organization.url}" />




Third party plugins must use a plugin weight greater than 100.

Rate this page: