Capabilities

• Sync user identities from GitLab to ConductorOne

• Resources supported:

  • Projects
  • Groups

Add a new GitLab connector

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

1. In ConductorOne, click Connectors > Add connector.

2. Search for GitLab and click Add.

3. Choose how to set up the new GitLab connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

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

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

   A GitLab connector owner must have the following permissions:

   • Connector Administrator or Super Administrator role in ConductorOne
   • Group Owner access in GitLab

5. Click Next.

Next steps

• If you are the connector owner, proceed to Configure your GitLab connector for instructions on integrating GitLab with ConductorOne.

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

Configure your GitLab connector

A user with the Connector 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, navigate to the GitLab connector by either:

   • Clicking the Set up connector link in the email you received about configuring the connector.

   • Navigate to Connectors > GitLab (if there is more than one GitLab listed, click the one with your name listed as owner and the status Not connected).

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

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

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

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

6. Click Save.

7. 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 connector is now pulling access data into 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.