Skip to content

Setting Up Gitlab for Access Control Integration

quentinvedrenne edited this page Mar 4, 2025 · 5 revisions

Overview

This guide will walk you through the steps to configure Gitlab for use with our access control system.

Prerequisites

Before starting, ensure that you meet the following requirements:

  • Gitlab Premium or Ultimate Account: IP allow lists are available only for organizations using Premium or Ultimate.
  • Admin Access: You must have administrative privileges in the Gitlab group.

Step 1: Create a Personal Access Token

To enable our system to communicate with the Gitlab API, you need to generate a personal access token.

  1. Log in to Gitlab.

  2. In the upper-left corner, click your profile photo, and select Preferences. Screenshot 2025-03-04 at 9 02 01 PM Screenshot 2025-03-04 at 9 02 45 PM

  3. In the left sidebar, click Access tokens. Screenshot 2025-03-04 at 9 03 24 PM

  4. Click "Add new token" Screenshot 2025-03-04 at 9 03 40 PM

  5. Select the "api" Screenshot 2025-03-04 at 9 04 06 PM

Step 2: Retrieve your gitlab organizationID

You'll need to know the id of your Gitlab Group to complete the integration.

  1. Log in to Gitlab.

  2. Go to the group tab Group and go to the settings. Screenshot 2025-03-04 at 9 08 27 PM Screenshot 2025-03-04 at 9 09 16 PM

  3. Click on Advanced Screenshot 2025-03-04 at 9 09 54 PM

  4. Copy the name of the group Screenshot 2025-03-04 at 9 10 28 PM

Step 3: Configure the Integration in EDAMAME Hub

  1. Visit the EDAMAME Hub.

  2. Select your domain.

  3. Navigate to the Policy section. Screenshot 2025-03-04 at 9 12 06 PM

  4. Click on the Conditional access tab.

  5. Click Add conditional access. Screenshot 2025-03-04 at 9 13 30 PM

  6. Select Gitlab and fill with the access token and. the organization name. Screenshot 2025-03-04 at 9 14 15 PM

Clone this wiki locally