GitLab
This documentation is maintained by the community, it is not guaranteed to be complete or up-to-date.
We always recommend users read the third-party documentation as part of the integration process to ensure the configuration matches their needs and as such we always link the documentation if available.
If you find an error in this documentation please either make a GitHub Pull Request or start a GitHub Discussion.
Tested Versions
Before You Begin
You are required to utilize a unique client id and a unique and random client secret for all OpenID Connect relying parties. You should not use the client secret in this example, you should randomly generate one yourself. You may also choose to utilize a different client id, it’s completely up to you.
This example makes the following assumptions:
- Application Root URL:
https://gitlab.example.com - Authelia Root URL:
https://auth.example.com - Client ID:
gitlab - Client Secret:
gitlab_client_secret
Configuration
Application
To configure GitLab to utilize Authelia as an OpenID Connect Provider:
- Add the Omnibus OpenID Connect OmniAuth configuration to
gitlab.rb:
gitlab_rails['omniauth_providers'] = [
{
name: "openid_connect",
label: "Authelia",
icon: "https://www.authelia.com/images/branding/logo-cropped.png",
args: {
name: "openid_connect",
scope: ["openid","profile","email","groups"],
response_type: "code",
issuer: "https://auth.example.com",
discovery: true,
client_auth_method: "query",
uid_field: "preferred_username",
send_scope_to_token_endpoint: "false",
client_options: {
identifier: "gitlab",
secret: "gitlab_client_secret",
redirect_uri: "https://gitlab.example.com/users/auth/openid_connect/callback"
}
}
}
]
Authelia
The following YAML configuration is an example Authelia client configuration for use with GitLab which will operate with the above example:
- id: gitlab
description: GitLab
secret: gitlab_client_secret
public: false
authorization_policy: two_factor
redirect_uris:
- https://gitlab.example.com/users/auth/openid_connect/callback
scopes:
- openid
- profile
- groups
- email
userinfo_signing_algorithm: none