docs/content/integration/openid-connect/clients/dashy/index.md
{{% oidc-common bugs="claims-hydration" %}}
This example makes the following assumptions:
https://dashy.{{< sitevar name="domain" nojs="example.com" >}}/https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/dashySome of the values presented in this guide can automatically be replaced with documentation variables.
{{< sitevar-preferences >}}
The following YAML configuration is an example Authelia client configuration for use with Dashy which will operate with the application example:
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: 'dashy'
client_name: 'Dashy'
public: true
authorization_policy: 'two_factor'
require_pkce: true
pkce_challenge_method: 'S256'
redirect_uris:
- 'https://dashy.{{< sitevar name="domain" nojs="example.com" >}}'
scopes:
- 'openid'
- 'profile'
- 'email'
- 'groups'
- 'roles'
grant_types:
- 'authorization_code'
response_types:
- 'code'
access_token_signed_response_alg: 'none'
userinfo_signed_response_alg: 'none'
token_endpoint_auth_method: 'none'
{{% oidc-escape-hatch-claims-hydration client_id="dashy" claims="email,email_verified,alt_emails,preferred_username,name" %}}
To configure Dashy there is one method, using the Configuration File.
To configure Dashy to utilize Authelia as an OpenID Connect 1.0 Provider, use the following configuration:
appConfig:
auth:
enableOidc: true
oidc:
clientId: 'dashy'
endpoint: 'https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}'