This document is about using GitLab as an OpenID Connect identity provider to sign in to other services.
OpenID Connect (OIDC) is a simple identity layer on top of the OAuth 2.0 protocol. It allows clients to:
- Verify the identity of the end-user based on the authentication performed by GitLab.
- Obtain basic profile information about the end-user in an interoperable and REST-like manner.
OIDC performs many of the same tasks as OpenID 2.0, but is API-friendly and usable by native and mobile applications.
The GitLab implementation uses the doorkeeper-openid_connect gem, refer to its README for more details about which parts of the specifications are supported.
Refer to the OAuth guide for basic information on how to set up OAuth
applications in GitLab. To enable OIDC for an application, all you have to do
is select the
openid scope in the application settings.
The following user information is shared with clients:
|The ID of the user|
|An opaque token that uniquely identifies the user|
Deprecation notice: this token isn’t stable because it’s tied to the Rails secret key base, and is provided only for migration to the new stable
|The timestamp for the user’s last authentication|
|The user’s full name|
|The user’s GitLab username|
|The user’s email address|
This is the user’s primary email address if the application has access to the
|Whether the user’s email address was verified|
|URL for the user’s website|
|URL for the user’s GitLab profile|
|URL for the user’s GitLab avatar|
|Paths for the groups the user is a member of, either directly or through an ancestor group.|
|Paths for the groups the user is a direct member of.|
groups_direct are included in the ID token. All other claims are available from the
/oauth/userinfo endpoint used by OIDC clients.