Threat Dragon version 2.0

GitLab repo testing

Home > Docs-2 > gitlab-repo

GitLab repository access

Most of steps are the same as the GitHub configuration but there are some parts that are different:

  1. Web App GitLab Access
  2. Environment variables

1. Web App GitLab Access

It’s recommended to follow the gitlab official guide to set up the OAuth Application.

The recommended configuration is similar to below:

  • Redirect URI: {BaseURL of your Threat Dragon Instance}/api/oauth/return
  • Scopes: Check read_user read_repository write_repository profile read_api api

Other options like Trusted are according to personal preference.

After finishing the OAuth Application you will get Application ID and Application Secret, which are used for the environment variables.

2. Environment variables

To help your threat dragon instance to support GitLab access, you have to set the environment variables like below

GITLAB_CLIENT_ID=00112233445566778899aabbccddeeff
GITLAB_CLIENT_SECRET=gloas-deadbeef0123456789abcdefdeadbeef
GITLAB_SCOPE=read_user read_repository write_repository profile read_api api
GITLAB_REDIRECT_URI=http://threat-dragon-instance/api/oauth/return
GITLAB_HOST=http://gitlab-instance

where:

  • GITLAB_CLIENT_ID: the Application ID you got from Gitlab
  • GITLAB_CLIENT_SECRET: the Application Secret you got from Gitlab
  • GITLAB_SCOPE: the functionalities you allow the threat dragon to use
  • GITLAB_REDIRECT_URI: set it like this pattern {BaseURL of your Threat Dragon Instance}/api/oauth/return
  • GITLAB_HOST: the BaseURL of your GitLab Instance, if you’re using official GitLab instance, remove this variable or set it to https://gitlab.com/

Now you have successfully configured the GitLab access for your Threat Dragon instance, for anything not mentioned in this guide check the GitHub configuration guide.

Watch Star