Safeguard Docs
Enterprise Software Supply Chain Manager (ESSCM)IntegrationsSource Code (SCM)

GitLab

Connect GitLab repositories to generate SBOMs

Permissions and token types

The GitLab integration guide lists the exact permissions each token needs, which token types work, and the current setup steps. Where this page and that guide differ, follow the guide.

GitLab Integration

Connect your GitLab repositories (cloud or self-hosted) to Safeguard for SBOM generation and vulnerability scanning.

Prerequisites

  • A GitLab account (gitlab.com or self-hosted instance)
  • For private repositories: Personal Access Token

Public Repositories

Step 1: Navigate to Integrations

Go to Integrations from the sidebar and click Connect on the GitLab card.

Step 2: Enter Repository URL

  1. Select the Public tab
  2. Enter a Name for this configuration
  3. Optionally add a Description
  4. Enter the public GitLab repository URL (e.g., https://gitlab.com/gitlab-org/gitlab)
  5. Click Add to add the URL to the list

Step 3: Review & Connect

  1. Review the added repository URLs
  2. Click Next to proceed
  3. Configure Branch/Tag, Project Name, and Version for each repository
  4. Click Connect to complete

Private Repositories

Step 1: Navigate to Integrations

Go to Integrations from the sidebar and click Connect on the GitLab card.

Step 2: Enter Credentials

  1. Select the Private tab
  2. Enter a Name for this configuration
  3. Optionally add a Description
  4. Enter the GitLab URL (for self-hosted instances, e.g., https://gitlab.yourcompany.com)
  5. Enter your Personal Access Token
  6. Click Verify Credentials

Step 3: Select Repositories

  1. Once credentials are verified, browse available groups/projects
  2. Select repositories to scan
  3. Configure Branch/Tag, Project Name, and Version
  4. Click Connect to complete

Creating a Personal Access Token

For GitLab.com

  1. Go to gitlab.com and sign in
  2. Click your profile picture then Edit profile
  3. In the left sidebar, click Access Tokens
  4. Click Add new token
  5. Enter a token name (e.g., "Safeguard Integration")
  6. Set an expiration date
  7. Select the required scopes:

Required Scopes

ScopeDescription
read_apiRead access to the API
read_repositoryRead access to repositories
  1. Click Create personal access token
  2. Copy the token immediately (it won't be shown again)

For Self-Hosted GitLab

  1. Navigate to your GitLab instance
  2. Go to User Settings then Access Tokens
  3. Follow the same process as GitLab.com

Self-Hosted GitLab Configuration

For self-hosted GitLab instances:

  1. Ensure your GitLab instance is accessible from Safeguard
  2. Use the full URL including protocol (e.g., https://gitlab.yourcompany.com)
  3. If using self-signed certificates, contact support for configuration options

Network Requirements

RequirementDetails
ProtocolHTTPS (recommended) or HTTP
Port443 (HTTPS) or 80 (HTTP) or custom
FirewallAllow outbound connections from Safeguard

Troubleshooting

"Credentials verification failed"

  • Verify the Personal Access Token has the required scopes
  • Ensure the token has not expired
  • For self-hosted: check the GitLab URL is correct and accessible

"SSL Certificate Error"

  • For self-hosted instances with self-signed certificates, contact support
  • Ensure the certificate chain is complete

"Project not found"

  • Verify you have access to the project in GitLab
  • Ensure the token has read_repository scope

GitHub

Connect GitHub repositories to generate SBOMs

Bitbucket

Connect Bitbucket repositories to generate SBOMs

On this page

GitLab IntegrationPrerequisitesPublic RepositoriesStep 1: Navigate to IntegrationsStep 2: Enter Repository URLStep 3: Review & ConnectPrivate RepositoriesStep 1: Navigate to IntegrationsStep 2: Enter CredentialsStep 3: Select RepositoriesCreating a Personal Access TokenFor GitLab.comRequired ScopesFor Self-Hosted GitLabSelf-Hosted GitLab ConfigurationNetwork RequirementsTroubleshooting"Credentials verification failed""SSL Certificate Error""Project not found"