Skip to main content
Back to Search AI connectors list GitLab is a DevOps platform used for version control, CI/CD, and collaborative software development, including issue tracking and management. Using the Search AI GitLab connector, you can index and search through issues tracked in your GitLab account.

​
Specifications

SpecificationDetails
Repository typeCloud
Supported contentIssues
RACL supportYes
Content filteringNo

​
Authorization Support

Search AI interacts with GitLab via APIs and supports the following authentication methods:
  • OAuth 2.0
  • Personal Access Token

​
Prerequisites

Sign in to your GitLab account and set up one of the following based on your chosen authorization type.

​
Personal Access Token

  1. Go to your profile (top left) and click Edit Profile.
  2. Go to Access Tokens in the left navigation menu.
  3. Click Add new token.
  4. Select the read_api scope and create the token.
Refer to the GitLab documentation for details.

​
OAuth 2.0

  1. Go to the Applications page under your user profile.
  2. Create a new app for Search AI integration.
  3. Set one of the following as the redirect URL based on your region:
    • JP Region: https://jp-bots-idp.kore.ai/workflows/callback
    • DE Region: https://de-bots-idp.kore.ai/workflows/callback
    • Prod: https://idp.kore.com/workflows/callback
  4. Select the read_api scope.
  5. This generates an application ID and client secret. Use these credentials to generate an access token and refresh token via an API client tool such as Postman. Refer to the GitLab OAuth2 authorization code flow for details.

​
Configure the GitLab Connector in Search AI

  1. Navigate to the Connectors page and select GitLab.
  2. Provide the following fields:
    FieldDescription
    NameUnique name for the connector
    Authorization TypePersonal Access Token (Private Token) or OAuth 2.0
    Token / Client CredentialsPersonal Access Token, or client credentials and access tokens for OAuth 2.0
  3. Click Connect to sync content from GitLab.

​
RACL Support

All ingested content is associated with the GitLab project it belongs to. The sys_racl field is set to the projectId for each piece of content. A permission entity is created for each project ID. Use the Permission Entity APIs to associate users with the corresponding permission entity to grant access to that project’s content.