Support for multiple domains / additional Traefik labels in Authentik service #916
Description
When deploying Authentik with mash-playbook, the Traefik configuration currently only supports a single domain.
This becomes a limitation in scenarios where Authentik needs to be available on multiple domains.
Example use case:
- Main domain:
auth.example.com - Branding domain:
brand.example.com
At the moment, there is no clear way to configure mash-playbook so that Authentik is reachable from both domains. Attempts to add the second domain result in Traefik returning 404.
What we would like to achieve
- Allow Authentik to be exposed on more than one domain (main + branding)
- Be able to configure these additional domains through inventory variables
- Ensure that Traefik correctly routes requests for all configured domains to the Authentik service