GitLab Self-Managed OAuth Setup

Use this guide to create the OAuth application Eureka needs before you configure a GitLab Self-Managed connection.

Note: This setup is only for GitLab Self-Managed instances. For gitlab.com, use the standard hosted GitLab connection instead.

Before you start

You will need:

  • Access to the GitLab Self-Managed instance where you want to create the OAuth application.
  • Permission to create or manage GitLab applications.

Create the OAuth application

  1. In your GitLab Self-Managed instance, open SettingsApplications.
  2. Create a new application for Eureka.
  3. Set the application name to something recognizable, such as Eureka DevSecOps.
  4. Set the Redirect URI to https://app.eurekadevsecops.com/connections/gitlab_self_managed/callback.
  5. Enable the required scopes listed below.
  • api
  • read_api
  • read_repository
  1. Save the application.

Connect GitLab Self-Managed in Eureka

After the GitLab application is created:

  1. In Eureka, click Settings in the top-right corner.
  2. Navigate to the Repositories section.
  3. Click the Add dropdown button and select GitLab Self Managed. This will open the GitLab Self Managed Connection Configuration Modal.
  4. Fill in the following fields:
    • Name — a display name for this connection (for example, the name of your GitLab Self-Managed instance).
    • Host — the base URL of your GitLab Self-Managed instance (for example, https://gitlab.example.com).
    • Application ID — copy this from the GitLab OAuth application you created.
    • Secret — copy this from the GitLab OAuth application you created.
  5. Save the configuration to complete the connection.