2.6 KiB
2.6 KiB
title | description | lead | date | draft | images | menu | weight | toc | community | ||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
GitLab | Integrating GitLab with the Authelia OpenID Connect Provider. | 2022-06-15T17:51:47+10:00 | false |
|
620 | true | true |
Tested Versions
Before You Begin
Common Notes
- You are required to utilize a unique client id for every client.
- The client id on this page is merely an example and you can theoretically use any alphanumeric string.
- You should not use the client secret in this example, We strongly recommend reading the [Generating Client Secrets] guide instead.
Assumptions
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: '$plaintext$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