Set up a GitLab connector
This version of the GitLab connector does not support account provisioning in GitLab Data Center. Please go to the GitLab Data Center connector for more information.
Capabilities
| Resource | Sync | Provision |
|---|---|---|
| Accounts | ✅ | |
| Projects | ✅ | |
| Groups | ✅ |
Gather GitLab credentials
Configuring the connector requires you to pass in credentials generated in GitLab. Gather these credentials before you move on.
A user with group Owner access in GitLab must perform this task.
Look up your GitLab group
In GitLab, click Menu > Groups > Your Groups.
Click on the group you wish to connect to ConductorOne.
Make a note of the Group Name or Group ID.
Create a personal access token
In the GitLab menu bar, click your profile photo then click Edit profile.
In the User Settings menu, click Access Tokens.
Give your token a name and set an expiration date.
In the Select scopes area, select read_api.
Click Create personal access token.
Carefully copy and save the newly created token.
That’s it! Next, move on to the connector configuration instructions.
Configure the GitLab connector
To complete this task, you’ll need:
- The Connector Administrator or Super Administrator role in ConductorOne
- Access to the set of GitLab credentials generated by following the instructions above
Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.
In ConductorOne, navigate to Admin > Connectors and click Add connector.
Search for GitLab and click Add.
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
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.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
Find the Settings area of the page and click Edit.
In the Group field, enter the name of your GitLab group.
Paste the token you into the Personal access token field.
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.
Click Save.
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.
Follow these instructions to use a connector, hosted and run in your own environment.
Self-hosted connector not currently available.