The value used in this guide is merely for readability and demonstration purposes and you should not use
this value in production and should instead utilize the How do I generate a client identifier or client secret?
FAQ. We recommend 64 random characters but you can use any arbitrary value that meets the other criteria.
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.
When the secret is stored in hashed form in the Authelia configuration (heavily recommended), the cost of
hashing can, if too great, cause timeouts for clients. See the
Tuning the work factors guide for more information.
The configuration example for Authelia:
Only contains an example configuration for the client registration and you MUST also configure the required
elements from the OpenID Connect 1.0 Provider Configuration guide.
Only contains a small portion of all of the available options for a registered client and users may wish to
configure portions that are not part of this guide or configure them differently, as such it’s important to
both familiarize yourself with the other options available and the effect of each of the options configured in
this section by looking at the OpenID Connect 1.0 Clients Configuration
guide.
This option determines the redirect URI in the format of
https://gitea.example.com/user/oauth2/<Authentication Name>/callback.
This means if you change this value you need to update the redirect URI.