Tested Versions

Before You Begin

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 demonstration purposes and you can theoretically use nearly any alphanumeric string.
  2. The OpenID Connect 1.0 secret parameter:
    1. 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.
    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. 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.


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.



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.


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

    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
    ## See:
    - id: firezone
      description: Firezone
      secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.
      public: false
      authorization_policy: two_factor
        - openid
        - email
        - profile
      userinfo_signing_algorithm: none

See Also