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, as well as to 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 does so in a way that is API-friendly, and usable by native and mobile applications.
GitLab’s 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.
Currently 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 public email address|
|Whether the user’s public email address was verified|
|URL for the user’s website|
|URL for the user’s GitLab profile|
|URL for the user’s GitLab avatar|
|Names of the groups the user is a member of|
sub_legacy claims are included in the ID token, all other claims are available from the
/oauth/userinfo endpoint used by OIDC clients.