Skip to main content

Connect GitLab

Use this guide to let Cracken read GitLab projects, work items, and vulnerability data.

Prerequisites​

  • Permission to create a GitLab personal, project, or group access token
  • Membership in every project or group you want Cracken to read
  • GitLab Ultimate and a completed security scan in each project whose vulnerabilities Cracken should read
  • A Cracken realm where you can configure data integrations

Prepare the token and URL​

Create a token with the read_api scope. The token inherits the user's or bot's project membership, so assign at least the role required to view the target projects and their vulnerability reports.

For GitLab.com, use https://gitlab.com as Base URL. For self-managed GitLab, use the instance URL. Keep Verify SSL enabled. If Cracken cannot validate a self-managed certificate, install the private certificate authority in the Cracken deployment's trust store before connecting.

Connect GitLab​

  1. Open Integration Center → Data Integrations.
  2. On the GitLab card, click Install.
  3. Enter the Access Token, Base URL, and Verify SSL setting.
  4. Click Test Connection, then Save & Connect.

Cracken can list accessible projects, issues, and merge requests. Vulnerability listing also requires GitLab Ultimate and completed security scans for the target projects.

Sources​

Next steps​

  • Data Integrations — Review how connected security data flows into Cracken.
  • Cybergraph — See how Cracken uses imported application data.