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

Ensure service account continuity

Create a dedicated application user

Arnica's Gitlab integration leverages a Gitlab 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


Grant permissions to application user

  1. Login to the Gitlab group

  2. Navigate to the Group Members page located in[YOUR_GROUP]/-/group_members

  3. Click on Invite Members , type the username or email of the dedicated service account, select an Owner role, and click on Invite

  1. Accept the invite by the dedicated service account.

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

Installation process

Generate a Personal Access Token

  1. Login with the application user and navigate to the Personal Access Tokens page.

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

  1. Click on Create personal access token

  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 Gitlab.

  2. Fill in the token from the step above.

  3. Click on Validate to ensure that the token works properly and then click on OK.

Arnica will integrate with all groups 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.

Last updated