docs/content/integration/openid-connect/clients/zammad/index.md
{{% oidc-common %}}
This example makes the following assumptions:
https://zammad.{{< sitevar name="domain" nojs="example.com" >}}/https://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}/zammadauthelia:
https://zammad.{{< sitevar name="domain" nojs="example.com" >}}/user/oauth2/<Authentication Name>/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.
{{< sitevar-preferences >}}
The following YAML configuration is an example Authelia client configuration for use with Zammad 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: 'zammad'
client_name: 'Zammad'
public: true
authorization_policy: 'two_factor'
require_pkce: true
pkce_challenge_method: 'S256'
redirect_uris:
- 'https://zammad.{{< sitevar name="domain" nojs="example.com" >}}/auth/openid_connect/callback'
scopes:
- 'openid'
- 'email'
- 'profile'
response_types:
- 'code'
grant_types:
- 'authorization_code'
access_token_signed_response_alg: 'none'
userinfo_signed_response_alg: 'none'
token_endpoint_auth_method: 'none'
To configure Zammad there is one method, using the Web GUI.
To configure Zammad to utilize Authelia as an OpenID Connect 1.0 Provider, use the following instructions:
Autheliazammadhttps://{{< sitevar name="subdomain-authelia" nojs="auth" >}}.{{< sitevar name="domain" nojs="example.com" >}}subyesopenid, email, profile