mirror of
https://github.com/0rangebananaspy/authelia.git
synced 2024-09-14 22:47:21 +07:00
bdb65318f2
Co-authored-by: James Elliott <james-d-elliott@users.noreply.github.com>
2.1 KiB
2.1 KiB
title | description | lead | date | draft | images | menu | weight | toc | community | ||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Gitea | Integrating Gitea with the Authelia OpenID Connect Provider. | 2022-07-01T13:07:02+10:00 | false |
|
620 | true | true |
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://gitea.example.com
- Authelia Root URL:
https://auth.example.com
- Client ID:
gitea
- Client Secret:
gitea_client_secret
Configuration
Application
To configure Gitea to utilize Authelia as an OpenID Connect Provider:
- Expand User Options
- Visit Site Administration
- Visit Authentication Sources
- Visit Add Authentication Source
- Configure:
- Authentication Name:
authelia
- OAuth2 Provider:
OpenID Connect
- Client ID (Key):
gitea
- Client Secret:
gitea_client_secret
- OpenID Connect Auto Discovery URL:
https://auth.example.com/.well-known/openid-configuration
- Authentication Name:
{{< figure src="gitea.png" alt="Gitea" width="300" >}}
Authelia
The following YAML configuration is an example Authelia client configuration for use with Gitea which will operate with the above example:
- id: gitea
secret: gitea_client_secret
public: false
authorization_policy: two_factor
scopes:
- openid
- email
- profile
redirect_uris:
- https://gitea.example.com/user/oauth2/authelia/callback
userinfo_signing_algorithm: none