Gitea

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:

  1. Expand User Options
  2. Visit Site Administration
  3. Visit Authentication Sources
  4. Visit Add Authentication Source
  5. Configure:
    1. Authentication Name: authelia
    2. OAuth2 Provider: OpenID Connect
    3. Client ID (Key): gitea
    4. Client Secret: gitea_client_secret
    5. OpenID Connect Auto Discovery URL: https://auth.example.com/.well-known/openid-configuration
Gitea

To configure Gitea to perform automatic user creation for the auth.example.com domain via OpenID Connect:

  1. Edit the following values in the Gitea app.ini:
[openid]
ENABLE_OPENID_SIGNIN = false
ENABLE_OPENID_SIGNUP = true
WHITELISTED_URIS     = auth.example.com

[service]
DISABLE_REGISTRATION                          = false
ALLOW_ONLY_EXTERNAL_REGISTRATION              = true
SHOW_REGISTRATION_BUTTON                      = false

Take a look at the See Also section for the cheatsheets corresponding to the sections above for their descriptions.

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

See Also