# Configuring the GitLab SaaS Connector

To connect GitLab to Agentic Fabric, you'll create an access token in GitLab. This will allow Agentic Fabric to discover access tokens and service accounts in GitLab and aggregate them as non-human identities and accounts.

!!! important

If your organization has already configured a GitLab SaaS source, you can use the existing source for agent discovery. The fields will be prepopulated with the source's information. You can edit these fields to configure a new integration.

## Creating an Access Token in GitLab

You can create a personal or group access token to complete the connection to Agentic Fabric. Refer to the GitLab [connector documentation](https://documentation.sailpoint.com/connectors/saas/gitlab/help/saas_connectivity/gitlab/prerequisites.html) for information on the best option for your use case.

**To create an access token in GitLab:**

1. Follow GitLab's product documentation to create a [personal access token](https://docs.gitlab.com/user/profile/personal_access_tokens/) *or* [group access token](https://docs.gitlab.com/user/group/settings/group_access_tokens/).

- Add the necessary roles to the token. Roles are applicable for both personal and group access tokens. Refer to [Prerequisites](https://documentation.sailpoint.com/connectors/saas/gitlab/help/saas_connectivity/gitlab/prerequisites.html) for information on the required role to aggregate specific data.
    - Add the `read_api` scope to the token. This scope is required for both personal and group access tokens. For more information about this scope, refer to [Access token scopes](https://docs.gitlab.com/security/tokens/access_token_scopes/).

2. Save the access token to a safe location. You'll provide the token to connect GitLab to Agentic Fabric.

## Connecting GitLab to Agentic Fabric

1. Go to the **Connect Source** step of the Agentic Fabric onboarding experience.
2. Select **GitLab SaaS** from the left pane.
3. In the **GitLab SaaS** section, complete the following:

- In the **Source Name** field, enter a unique name for the source.

- In the **Source Owner** field, select the identity who will own the source.

- In the **Description** field, enter a unique description for the source to distinguish it from similar connections.

4. In the **Configure Authentication** section, complete the following:

- In the **Base URL** field, enter the base URL of your GitLab instance (`https://gitlab.example.com` or `https://gitlab.com`).

- Select the **Self Managed** toggle if the source points to a customer-run instance rather than `gitlab.com`.

- For **Authentication Type**, select **Personal Access Token** or **Group Access Token**.
  
    - In the **Access Token** field, enter the access token you created.

- In the **Target Groups** field, enter the target groups as group full paths or numeric group IDs. Refer to the GitLab product documentation for information on [groups](https://docs.gitlab.com/user/group/) and [finding a group ID](https://docs.gitlab.com/user/group/#find-the-group-id).

!!! note

Subgroups and their projects are included automatically, so name only the top of each tree you want.

5. Select **Test Connection** to ensure the connection is successful.

6. If the test is successful, select **Aggregate** to run an aggregation for the source. Select **Exit** to skip this step. You can configure aggregations for the source's [datasets](../../../sources/datasets.md#configuring-dataset-aggregations) later in the source's configuration.

A **Completed** status is now displayed next to the source in the left panel.

7. Choose another connector to configure or select **Continue** to proceed to the next onboarding step.

Configuring the GitLab SaaS Connector

To connect GitLab to Agentic Fabric, you'll create an access token in GitLab. This will allow Agentic Fabric to discover access tokens and service accounts in GitLab and aggregate them as non-human identities and accounts.

Important

If your organization has already configured a GitLab SaaS source, you can use the existing source for agent discovery. The fields will be prepopulated with the source's information. You can edit these fields to configure a new integration.

Creating an Access Token in GitLab

You can create a personal or group access token to complete the connection to Agentic Fabric. Refer to the GitLab connector documentation for information on the best option for your use case.

To create an access token in GitLab:

Follow GitLab's product documentation to create a personal access token or group access token.
- Add the necessary roles to the token. Roles are applicable for both personal and group access tokens. Refer to Prerequisites for information on the required role to aggregate specific data.
- Add the read_api scope to the token. This scope is required for both personal and group access tokens. For more information about this scope, refer to Access token scopes.
Save the access token to a safe location. You'll provide the token to connect GitLab to Agentic Fabric.

Connecting GitLab to Agentic Fabric

Go to the Connect Source step of the Agentic Fabric onboarding experience.
Select GitLab SaaS from the left pane.
In the GitLab SaaS section, complete the following:
- In the Source Name field, enter a unique name for the source.
- In the Source Owner field, select the identity who will own the source.
- In the Description field, enter a unique description for the source to distinguish it from similar connections.
In the Configure Authentication section, complete the following:
- In the Base URL field, enter the base URL of your GitLab instance (https://gitlab.example.com or https://gitlab.com).
- Select the Self Managed toggle if the source points to a customer-run instance rather than gitlab.com.
- For Authentication Type, select Personal Access Token or Group Access Token.
- In the Access Token field, enter the access token you created.
- In the Target Groups field, enter the target groups as group full paths or numeric group IDs. Refer to the GitLab product documentation for information on groups and finding a group ID.
  
  Note
  
  Subgroups and their projects are included automatically, so name only the top of each tree you want.
Select Test Connection to ensure the connection is successful.
If the test is successful, select Aggregate to run an aggregation for the source. Select Exit to skip this step. You can configure aggregations for the source's datasets later in the source's configuration.

A Completed status is now displayed next to the source in the left panel.
Choose another connector to configure or select Continue to proceed to the next onboarding step.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.