This integration guide is community supported. It's not guaranteed to be complete, accurate, or up-to-date. It's likely that if this integration guide does not work for you that changes occurred with a third-party application.

Important Note: This documentation is version specific. Make sure you check the section outlining the tested versions.

Important Note: We always recommend users read the third-party documentation as part of the integration process to ensure configuration elements matches their needs. As such the See Also section is likely to have important links.

Important Note: If you find an error in this documentation please make a Pull Request, start a Discussion, or contact us on a Chat Room.

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: firezone
  • Client Secret: insecure_secret
  • Config ID (Firezone): authelia:
    • This option determines the redirect URI in the format of<Config ID>/callback. This means if you change this value you need to update the redirect URI.

Some of the values presented in this guide can automatically be replaced with documentation variables.



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

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


To configure Firezone to utilize Authelia as an OpenID Connect 1.0 Provider:

  1. Visit your Firezone site
  2. Sign in as an admin
  3. Visit:
    1. Settings
    2. Security
  4. In the Single Sign-On section, click on the Add OpenID Connect Provider button
  5. Configure:
    1. Config ID: authelia
    2. Label: Authelia
    3. Scope: openid email profile
    4. Client ID: firezone
    5. Client secret: insecure_secret
    6. Discovery Document URI:
    7. Redirect URI (optional):
    8. Auto-create users (checkbox): true

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

See Also