Announcing: Access Conflicts

ConductorOne Docs

GitLab integration

ConductorOne provides identity governance for GitLab. Integrate your GitLab instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.

Availability

General availability. The GitLab integration is available to all ConductorOne users.

Capabilities

  • Sync user identities from GitLab to ConductorOne

  • Resources supported:

    • Roles

Set up the GitLab integration

This task requires either the Integration Administrator or Super Administrator role in ConductorOne.

  1. In ConductorOne, open Admin and click Integrations > GitLab.

  2. If this is your first GitLab integration, the integration form opens automatically. Otherwise, click Add connector.

  3. Choose whether to add the new GitLab connector as a data source to an existing application (and select the app of your choice) or to create a new application.

    Do you SSO into GitLab using your identity provider (IdP)? If so, make sure to add the connector to the GitLab app that was created automatically when you integrated your IdP with ConductorOne, rather than creating a new app.

  1. Set the integration owner for this connector. You can manage the integration yourself, or choose someone else from the list of ConductorOne users. Setting multiple integration owners is allowed.

    A GitLab integration owner must have the following permissions:

    • Integration Administrator or Super Administrator role in ConductorOne
    • Group Owner access in GitLab
  1. Click Create and add details.

Next steps

  • If you are the integration owner, proceed to Integrate your GitLab instance for instructions on integrating GitLab with ConductorOne.

  • If someone else is the integration owner, ConductorOne will notify them by email that their help is needed to complete the integration.

Integrate your GitLab instance

A user with the Integration Administrator or Super Administrator role in ConductorOne and group Owner access in GitLab must perform this task.

Step 1: Look up your Gitlab group

  1. In GitLab, click Menu > Groups > Your Groups.

  2. Click on the group you wish to connect to ConductorOne.

  3. Make a note of the Group Name or Group ID. We’ll use this in Step 3.

Step 2: Create a personal access token

  1. In the GitLab menu bar, click your profile photo then click Edit profile.

  2. In the User Settings menu, click Access Tokens.

  3. Give your token a name and set an expiration date.

  4. In the Select scopes area, select read_api.

  5. Click Create personal access token.

  6. Carefully copy and save the newly created token. We’ll use this in Step 3.

Step 3: Add your GitLab credentials to ConductorOne

  1. In ConductorOne, open Admin and click Integrations > GitLab.

  2. In the list of connectors, locate and click on the name of the connector with the Not connected label.

  3. Find the Settings area of the page and click Edit.

  4. In the Group field, enter the name of your GitLab group.

  5. Paste the token you generated in Step 2 into the Personal access token field.

  6. Optional. If you need to point this integration to a private URL (such as a self-managed GitLab instance), enter the target URL in the URL field.

  7. Click Save.

  8. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your GitLab instance is now integrated with ConductorOne.

Configure the GitLab integration using Terraform

As an alternative to the integration process described above, you can use Terraform to configure the integration between GitLab and ConductorOne.

See the ConductorOne GitLab integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.