Gitea
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 start a Discussion, make a Pull Request, or contact us on a Chat Room.
Tested Versions
Before You Begin
Common Notes
- The OpenID Connect 1.0
client_id
parameter:- This must be a unique value for every client.
- The value used in this guide is merely for demonstration purposes and you can theoretically use nearly any alphanumeric string.
- The OpenID Connect 1.0
secret
parameter:- The value used in this guide is merely for demonstration purposes and you should absolutely not use this in production and should instead utilize the How Do I Generate Client Secrets FAQ.
- This string may be stored as plaintext in the Authelia configuration but this behaviour is deprecated and is not guaranteed to be supported in the future. See the Plaintext guide for more information.
- The Configuration example for Authelia is only a portion of the required configuration and it should be used as a guide in conjunction with the standard OpenID Connect 1.0 Configuration guide.
Assumptions
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:
insecure_secret
Configuration
Application
To configure Gitea to utilize Authelia as an OpenID Connect 1.0 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:
insecure_secret
- OpenID Connect Auto Discovery URL:
https://auth.example.com/.well-known/openid-configuration
- Authentication Name:

To configure Gitea to perform automatic user creation for the auth.example.com
domain via OpenID Connect 1.0:
- 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:
identity_providers:
oidc:
## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
## See: https://www.authelia.com/c/oidc
clients:
- id: gitea
description: Gitea
secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng' # The digest of 'insecure_secret'.
public: false
authorization_policy: two_factor
redirect_uris:
- https://gitea.example.com/user/oauth2/authelia/callback
scopes:
- openid
- email
- profile
userinfo_signing_algorithm: none
See Also
- Gitea app.ini Config Cheat Sheet: