Connecting to GitLab

Edit online

GitLab is a widely used DevOps platform that enables teams to manage source code, CI/CD pipelines, and project collaboration in a unified environment. Integrating IBM watsonx Orchestrate with GitLab allows seamless automation, secure authentication, and streamlined development workflows across your enterprise systems.

To integrate GitLab with IBM watsonx Orchestrate, you need to establish a secure connection that enables both systems to communicate seamlessly. For general guidance on managing integrations, refer to Connecting apps for prebuilt agents.

Important:

By default, Single sign-on (SSO) is disabled for your app. To enable it, refer to Configuring single sign-on for applications.

Steps to connect

Use the following steps to connect GitLab to watsonx Orchestrate:

  1. Go to Manage > Connections and search for the corresponding GitLab Connection ID.

  2. Click edit next to the matching connection ID.

  3. Select OAuth2 Authorization Code as the authentication type.

  4. Enter the GitLab‑specific fields described in the connection details section. See Connecting apps for prebuilt agents page for general connection workflow.

  5. Complete the Draft and Live setup steps.

  6. Save and test the connection to confirm successful connection.

Supported authentication methods

GitLab supports the following authentication type in watsonx Orchestrate:

  1. OAuth2 Authorization Code (recommended for production use)

Connection ID

Use the following Connection ID when locating your GitLab connection in the Connections settings page. To understand how to search for a Connection ID and open a connection for editing, see Connecting apps for prebuilt agents.

Authentication type

Connection ID

OAuth2 Authorization Code

``gitlab_oauth2_auth_code_ibm_184bdbd3``

OAuth 2.0 connection details

If your organization uses OAuth‑based authentication, set Authentication type to OAuth2 Authorization Code and enter the following fields:

Field

Description

server_url

The base URL of your GitLab instance

authorization_url

The URL where users are redirected to log in and authorize access

token_url

The endpoint used to exchange the authorization code for an access token

client_id

The client ID of your GitLab OAuth application

client_secret

The client secret associated with your GitLab OAuth application

You can obtain these values by creating an OAuth application in GitLab. Refer to the GitLab API documentation for more details.