ContextQMD
Back to Authelia

KitchenOwl

docs/content/integration/openid-connect/clients/kitchenowl/index.md

4.39.193.5 KB
Original Source

Tested Versions

{{% oidc-common %}}

Assumptions

This example makes the following assumptions:

  • Application Root URL: https://kitchenowl.{{< sitevar name="domain" nojs="example.com" >}}/
    • This option determines the redirect URI in the format of https://kitchenowl.{{< sitevar name="domain" nojs="example.com" >}}/signin/redirect. This means if you change this value, you need to update the redirect URI.
  • Authelia Root URL: https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/
  • Client ID: kitchenowl
  • Client Secret: insecure_secret

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

{{< sitevar-preferences >}}

Configuration

Authelia

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

yaml
identity_providers:
  oidc:
    ## The other portions of the mandatory OpenID Connect 1.0 configuration go here.
    ## See: https://www.authelia.com/c/oidc
    clients:
      - client_id: 'kitchenowl'
        client_name: 'KitchenOwl'
        client_secret: '$pbkdf2-sha512$310000$c8p78n7pUMln0jzvd4aK4Q$JNRBzwAo0ek5qKn50cFzzvE9RXV88h1wJn5KGiHrD0YKtZaR/nCb2CJPOsKaPK0hjf.9yHxzQGZziziccp6Yng'  # The digest of 'insecure_secret'.
        public: false
        authorization_policy: 'two_factor'
        require_pkce: false
        pkce_challenge_method: ''
        redirect_uris:
          - 'https://kitchenowl.{{< sitevar name="domain" nojs="example.com" >}}/signin/redirect'
          - 'kitchenowl:/signin/redirect'
        scopes:
          - 'openid'
          - 'profile'
          - 'email'
        response_types:
          - 'code'
        grant_types:
          - 'authorization_code'
        access_token_signed_response_alg: 'none'
        userinfo_signed_response_alg: 'none'
        token_endpoint_auth_method: 'client_secret_post'

Application

To configure KitchenOwl there is one method, using Environment Variables.

Environment Variables

To configure KitchenOwl to utilize Authelia as an OpenID Connect 1.0 Provider, use the following environment variables:

Standard
shell
FRONT_URL=https://kitchenowl.{{< sitevar name="domain" nojs="example.com" >}}
OIDC_ISSUER=https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}
OIDC_CLIENT_ID=kitchenowl
OIDC_CLIENT_SECRET=insecure_secret
Docker Compose
yaml
services:
  kitchenowl:
    environment:
      FRONT_URL: 'https://kitchenowl.{{< sitevar name="domain" nojs="example.com" >}}'
      OIDC_ISSUER: 'https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}'
      OIDC_CLIENT_ID: 'kitchenowl'
      OIDC_CLIENT_SECRET: 'insecure_secret'

See Also