Ctrlk
Book a demoOX Security
For the complete documentation index, see llms.txt. This page is also available as Markdown.

GitLab Identity Provider

Use this connection method to connect GitLab to OX using OAuth authentication. During the connection process, you authenticate to GitLab and grant OX access to the GitLab resources that you want to scan.

Before you begin

Verify that:

  • You have permission to configure connectors in OX.

  • You have access to the GitLab projects and groups that you want OX to scan.

Connect GitLab to OX

  1. In OX, go to Settings > Connections.

  2. Select GitLab > Identity Provider.

  1. In Connection Name, enter a name for the connection.

  2. Select Connect.

Note

When you select Connect, GitLab prompts you to authorize OX to access your organization's resources. You must explicitly approve this access to complete the connection.

GitLab SSO session requirements

When you connect GitLab to OX using the Identity Provider authentication method, OX accesses GitLab on behalf of the user who created the connection.

If your organization requires users to authenticate to GitLab through Single Sign-On (SSO), the GitLab session for the connected user must remain valid for OX to access repositories.

How it works

If GitLab is configured to require SSO through an Identity Provider (IdP):

  1. A user connects GitLab to OX using the Identity Provider authentication method.

  2. OX uses that user's GitLab authorization when accessing repositories.

  3. OX can clone repositories only while the user's GitLab SSO session remains valid.

If the GitLab SSO session expires, OX can no longer authenticate to GitLab and repository scans fail until the user signs in to GitLab again.

For example, if your organization configures GitLab SSO sessions to expire every 24 hours, the user who connected GitLab to OX must sign in to GitLab again at least every 24 hours to keep repository scanning working.

Important:

If repository scans unexpectedly stop working after an SSO session expires, have the user who connected the GitLab integration sign in to GitLab again to refresh the SSO session.

Recommended approach for organizations with short SSO sessions

If your organization enforces short-lived GitLab SSO sessions or frequent reauthentication, OX recommends connecting GitLab using a Token created for a dedicated service account instead of using the Identity Provider authentication method.

Using a service account token provides more reliable access for automated repository scanning because it does not depend on an individual user's active GitLab SSO session.

Last updated