Self-Hosted GitLab Integration

Self-hosted GitLab enables organisations to manage source code, CI/CD pipelines, and collaboration within privately hosted infrastructure.

The Sprinto self-hosted GitLab integration allows you to:

• Monitor production-classified repositories
• Enforce peer review before merges
• Validate status checks before merging
• Enforce branch protection rules
• Verify group-level MFA
• Detect and remove offboarded user access

Self-hosted GitLab supports Change Management only.

Sprinto checks for Gitlab integration

Following are the available Sprinto checks for GitLab integration:

How It Works

The integration uses an OAuth application created in your self-hosted GitLab instance.

1. You create a GitLab OAuth application.
2. You configure redirect URLs and scopes.
3. You provide Sprinto with:
   • Hosted service URL
   • Application ID
   • Client Secret
4. Sprinto securely connects and begins monitoring repository configuration metadata.

Sprinto evaluates configuration settings only. It does not modify repositories.

Before You Begin

Ensure that:

• You have a paid self-hosted GitLab account.
• You have Admin access to the GitLab instance.
• Sprinto’s IP address is allowlisted if your instance is not publicly accessible.
• You can create OAuth applications in GitLab.

Permissions Required (OAuth Scopes)

When creating the OAuth application in GitLab, select:

• read_api
• read_repository
• read_user
• profile

These permissions allow Sprinto to:

• Read groups and projects
• Evaluate branch protection rules
• Validate peer review enforcement
• Retrieve user access metadata

Sprinto does not request write access.

Dashboard Actions

Step 1: Create an OAuth Application in Self-Hosted GitLab

1. Log in to your self-hosted GitLab instance.
2. Click Menu.
3. Select Admin.
4. Go to Applications.
5. Click New application.

Enter the following details:

Name
Sprinto Audit

Redirect URL (Based on Region)

Enter one URL per line.

Select the following options:

• Trusted
• Confidential
• Expire access tokens

Select these scopes:

• read_user
• read_api
• read_repository
• profile

Click Save.

After saving:

• Copy the Application ID.
• Copy the Secret.
• Store them securely.

Step 2: Connect Self-Hosted GitLab in Sprinto

1. Log in to Sprinto.
2. Navigate to Settings > Integrations.
3. In the All tab, search for GitLab.
4. Click Connect next to GitLab (Version Control | Access Review).

Review Permissions

In the connection drawer:

• Review permissions required.
• Review data used by Sprinto.
• Click Next.

Step 3: Select Self-Hosted GitLab

On the Setup GitLab Integration screen:

You will see:

• Connection type: OAuth
• Prerequisites

Select:

Are you using self-hosted GitLab Service?

When selected, the following fields appear:

• Hosted service URL
• Application ID
• Client Secret

If you deselect this checkbox, these fields disappear and the integration defaults to GitLab Cloud.

Enter the following:

Hosted Service URL
Enter your domain without http:// or https://.

Example:
If your hosted URL is:
https://gitlab.company.com

Enter:
gitlab.company.com

Application ID
Enter the ID copied from GitLab.

Client Secret
Enter the secret copied from GitLab.

Review your details and click Connect.

You are now successfully integrated with self-hosted GitLab.

IP Allowlist (If Required)

If your hosted GitLab instance is restricted, allowlist the appropriate Sprinto IP:

Post-Connection Configuration

After connecting, configure GitLab as a Change Management system.

Configure GitLab for Change Management

1. Navigate to Data Library > Change Management.
2. Click Add system.
3. Click Add next to GitLab.
4. Select repositories to monitor.
5. Save your changes.

Sprinto will monitor:

• Peer review enforcement
• Merge request status checks
• Branch protection rules
• MFA enforcement
• Offboarded user access removal

Sync Timeline

After configuration:

• Initial sync begins automatically.
• Allow 15–20 minutes for initial data sync.
• Full evaluation may take up to 24 hours.

To manually refresh:

1. Navigate to Data Library > Change Management > GitLab.
2. Click Sync.

Sprinto Checks Supported

This integration validates:

• GitLab group-level MFA enforcement
• Peer review before merge
• Mandatory passing status checks
• Branch protection enforcement for admins
• Offboarded user access removal

Troubleshooting

Hosted service URL not accepted

• Remove http:// or https://.
• Ensure the domain is reachable from Sprinto.
• Verify firewall rules.

Connection fails after clicking Connect

• Confirm Application ID and Client Secret are correct.
• Verify redirect URL exactly matches your Sprinto region.
• Confirm scopes are correctly selected.

No repositories appear

• Ensure repositories belong to accessible groups.
• Confirm the OAuth application has required scopes.
• Trigger a manual sync.

Integration connected but checks not running

• Ensure GitLab is added under Change Management.
• Allow up to 24 hours for evaluation.
• Confirm repositories are properly classified in Sprinto.

Contact Sprinto support if you have queries related to the integration or need any assistance.