Tested Versions

Before You Begin

Important Reading

This section contains important elements that you should carefully consider before configuration of an OpenID Connect 1.0 Registered Client.

Common Notes

  1. The OpenID Connect 1.0 client_id parameter:
    1. This must be a unique value for every client.
    2. 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.
    3. This must only contain RFC3986 Unreserved Characters.
    4. This must be no more than 100 characters in length.
  2. The OpenID Connect 1.0 client_secret parameter:
    1. The value used in this guide is merely for demonstration purposes and you should absolutely not use this value in production and should instead utilize the How do I generate a client identifier or client secret? FAQ.
    2. 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.
    3. 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.
  3. The configuration example for Authelia:
    1. 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.
    2. 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 example makes the following assumptions:

  • Application Root URL:
  • Authelia Root URL:
  • Client ID: freshrss
  • Client Secret: insecure_secret
  • Port: ‘443’
    • This is the port FreshRSS is served over (usually 80 for http and 443 for https) NOT the port of the container.

Special Notes

  1. The FreshRSS implementation seems to always include the port in the requested redirect_uri. As Authelia strictly conforms to the specifications this means the client registration MUST include the port for the requested redirect_uri to match.



The following YAML configuration is an example Authelia client configuration for use with FreshRSS which will operate with the application example:

    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
    ## See:
      - client_id: 'freshrss'
        client_name: 'freshrss'
        client_secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.
        public: false
        authorization_policy: 'two_factor'
          - ''
          - 'openid'
          - 'groups'
          - 'email'
          - 'profile'
        userinfo_signed_response_alg: 'none'
        token_endpoint_auth_method: 'client_secret_basic'


  1. To configure FreshRSS to utilize Authelia as an OpenID Connect 1.0 Provider, specify the below environment variables.
  2. Open the newly created FreshRSS instance.
  3. During initial config, select “HTTP” during the user creation
  OIDC_CLIENT_ID: freshrss
  OIDC_CLIENT_SECRET: insecure_secret
  OIDC_REMOTE_USER_CLAIM: preferred_username
  OIDC_SCOPES: openid groups email profile
  OIDC_X_FORWARDED_HEADERS: X-Forwarded-Host X-Forwarded-Port X-Forwarded-Proto

See Also