Bitbucket Cloud


Arnicaโ€™s Bitbucket Cloud integration accesses selected environments to extract the necessary data and take remediation actions.

Ensure service account continuity

Create a dedicated application user

Arnica's Bitbucket integration leverages a Bitbucket generated app password tied to a specified user. To avoid the revocation of this token upon the impersonated user's departure, it is highly recommended to create and integrate using a standard application user.

The created user will be visible to all developers as part of Arnica's interactions, such as comments on merge requests. Hence, it is recommended to name the service account properly, such as arnica-service-account


IP allowlist

In some cases, customers may use IP allowlist to restrict which source IP addresses can access a specific workspace. To validate this functionality, navigate to[WORKSPACE_NAME]/workspace/settings/access-controls and check the IP allowlisting configuration.

Grant permissions to application user

  1. Login to the Bitbucket Cloud workspace

  2. Navigate to the User Groups page located in[YOUR_WORKSPACE]/workspace/settings/groups

  3. Click on the Administrators group and add the dedicated application security user to this group.

The following step will reduce the scope of the token to least privileges. This means that while the user will be assigned with administrator privileges, the token's privilege's will include a reduced scope.

If your environment is comprised of multiple workspaces, repeat the steps above for each workspace with the same user.

Installation process

Generate an app password

  1. Login with the application user and navigate to the app passwords page.

  2. Click on Create App Password and assign the following permissions to the token:

  1. Click on Create

  2. Copy the credentials into a temporary place to use them later in the integration


  1. Navigate to the Integrations page in Arnica and click on Bitbucket Cloud.

  2. Fill in the username (not email) and the app password from the step above.

  3. Click on Validate to ensure that the credentials work properly and then click on OK.

The username used to complete the integration should be the Bitbucket username (not the account email) of the user or application user that created the app password.

Arnica will integrate with all workspaces associated with this user. Arnica's default policies include scan-only functionality. While scanning will begin immediately, developers will not see any impact until Arnica's polices are updated to take actions.


Q: Why the service account needs to have administrative permissions? A: While the service account is granted with administrative permissions, the app token that is used by Arnica has least privileges. It was designed this way to maintain

Last updated