Authentication Through Gitlab

Overview

GitLab is a web-based Git repository manager with wiki and issue tracking features, using an open source license, developed by GitLab Inc. One of the login options for dex uses the GitLab OAuth2 flow to identify the end user through their GitLab account. You can use this option with gitlab.com, GitLab community or enterprise edition.

When a client redeems a refresh token through dex, dex will re-query GitLab to update user information in the ID Token. To do this, dex stores a readonly GitLab access token in its backing datastore. Users that reject dex’s access through GitLab will also revoke all dex clients which authenticated them through GitLab.

Configuration

Register a new application via User Settings -> Applications ensuring the callback URL is (dex issuer)/callback. For example if dex is listening at the non-root path https://auth.example.com/dex the callback would be https://auth.example.com/dex/callback.

The application requires the user to grant the read_user and openid scopes. The latter is required only if group membership is a desired claim.

The following is an example of a configuration for examples/config-dev.yaml:

  1. connectors:
  2.   - type: gitlab
  3.     # Required field for connector id.
  4.     id: gitlab
  5.     # Required field for connector name.
  6.     name: GitLab
  7.     config:
  8.       # optional, default = https://gitlab.com
  9.       baseURL: https://gitlab.com
  10.       # Credentials can be string literals or pulled from the environment.
  11.       clientID: $GITLAB_APPLICATION_ID
  12.       clientSecret: $GITLAB_CLIENT_SECRET
  13.       redirectURI: http://127.0.0.1:5556/dex/callback
  14.       # Optional groups whitelist, communicated through the "groups" scope.
  15.       # If `groups` is omitted, all of the user's GitLab groups are returned when the groups scope is present.
  16.       # If `groups` is provided, this acts as a whitelist - only the user's GitLab groups that are in the configured `groups` below will go into the groups claim.  Conversely, if the user is not in any of the configured `groups`, the user will not be authenticated.
  17.       groups:
  18.       - my-group
  19.       # flag which will switch from using the internal GitLab id to the users handle (@mention) as the user id.
  20.       # It is possible for a user to change their own user name but it is very rare for them to do so
  21.       useLoginAsID: false