Configure GitLab for external content indexing

Create a personal access token for a group owner user account on GitLab.com to allow the GitLab external content connector to access your GitLab source system.

Avant de commencer

To use the GitLab external content connector, your GitLab plan must satisfy all of these conditions:

Offering

You must be using the GitLab.com offering, not GitLab Dedicated or GitLab Self-Managed.

To learn more about GitLab offerings, see https://docs.gitlab.com/subscriptions/choosing_subscription/#choose-an-offering.

Group owner user account

You need a GitLab.com user account that owns all the public and private top-level groups you want the external content connector to crawl. The connector impersonates this user when retrieving searchable content, user access permissions, and security principals from your GitLab source system.

Public content requirements

Public content you want to retrieve must be in public top-level groups owned by your group owner user.

Private content requirements

Private content you want to retrieve must be in a private top-level group on the Ultimate subscription tier. This group must be owned by your group owner user, and you must have configured access permissions for enterprise users in this private group. (The connector only retrieves user access permissions and security principals for enterprise users.)

To learn more about GitLab subscription tiers, see https://docs.gitlab.com/subscriptions/choosing_subscription/#choose-a-subscription-tier. For information about GitLab enterprise users, see https://docs.gitlab.com/user/enterprise_user/.

You need login credentials for the group owner user account in your organization's GitLab.com instance.

Role required: none

Pourquoi et quand exécuter cette tâche

The GitLab external content connector retrieves content from your GitLab.com source system using the GitLab API and a personal access token with the read_api scope configured for the user account that owns all top-level groups you want to crawl. The connector uses this personal access token to impersonate the specified user when retrieving searchable content and security principals from your GitLab.com source system.

Your ServiceNow AI Platform instance admin needs this personal access token to configure the GitLab external content connector for proper connection to your GitLab.com source system.

Procédure

1. Log in to https://gitlab.com/ as the user that owns all top-level groups you want to retrieve searchable content from.
2. In the menu, select your avatar, then select Edit profile.
   
3. Select Access tokens, then select Add new token.
   
4. Enter a name, optional description, and expiration date for your new personal access token.
   Remarque :

   If you don't enter an expiration date, the token's expiration date is automatically set to 365 days later than the current date.
5. Select the read_api scope for your new personal access token.
6. Select Create token.
   
7. When prompted, select the copy icon to copy your new personal access token, then save it in a secure location.
   

   Important :

   Your connector admin needs this personal access token to create a GitLab external content connector. You won't be able to access the token again after creating it.

Que faire ensuite

Provide the following items to your connector admin:

• The URL for your GitLab instance. This is typically https://gitlab.com/.
• The personal access token for the group owner user that you copied in step 7.

Your connector admin needs these items to configure a GitLab external content connector to retrieve searchable content and security principals from your GitLab.com instance.

For details on creating and configuring a GitLab external content connector, see Create a GitLab external content connector.