This integration will be accessible starting November 10.
Overview
This guide explains how to connect GitLab with Grip Security. Integrating with Grip’s SSPM module enables Grip to assess critical security settings, including access control, configuration baseline, and other relevant aspects within your GitLab environment.
To connect to Grip, you will need to create a new application in GitLab and provide its Client ID and secret.
Prerequisites
Admin user in the GitLab account.
Create A new application in GitLab
Log in to your GitLab account
From your user settings, go to Edit Profile (1)
Go to Applications (2) » Add new application (3)
In the Application window, give the application a Name (4)
In the Redirect URl field (5), enter your Grip domain name after the “
https://”https://
{client_domain_in_grip}.integrations.grip.security/oauth/callback
For example, in this URL, https://acme.dep.grip.security/, the {client_domain_in_grip} will be, acme
Ensure the Confidential checkbox is checked
Check the
read_apicheckbox (6)Save the application (7)
Once saved, the application window will appear with the Application ID and Secret. Copy them, as you'll need them later to connect to Grip.
Connect GitLab to Grip SSPM
From the Grip platform, go to Posture >> Click on Add Tenant (1) » GitLab (2)
In the Add New GitLab Tenant window (3), enter the GitLab tenant Display name,
Enter the Application ID and Client Secret you copied in the previous section.
Click on Continue
The “Connect GitLab” window indicates that to complete the integration, you need to sign in to GitLab with your username and password or send a URL to the GitLab admin.
Once the admin approves it, the tenant will be connected.
Note that the link expires after one hour.
Once connected, the Tenant will be added to the “Connected Tenants” list. There, you can view and filter your policy statuses, assess your security posture, and address any issues.
