were you able to get the the traefik forward auth working with zitadel, so that all applications routed from traefik are protected by default in the homelab like scenarios
Hi, it is generally suggested to configure applications individually with single sign on config, but as some applications may not support it, you can use the forward auth middleware instead. To do this, you will need to add another middleware to the traefik's docker compose config and let it handle the authentication requests. It will require the redirect uri, client id and the client secret in the environment variables. You will also need to add the redirect uri's for each application you want to use in the zitadel configuration. Then you can use this middleware in the docker compose labels of you applications. For this, you can use thomseddon/traefik-forward-auth container to route the authentication requests. I know it's hard to explain over a comment so i'll try to post a video on it soon. Hope this helps for the time being !
Good Work Buddy
were you able to get the the traefik forward auth working with zitadel, so that all applications routed from traefik are protected by default in the homelab like scenarios
Hi, it is generally suggested to configure applications individually with single sign on config, but as some applications may not support it, you can use the forward auth middleware instead.
To do this, you will need to add another middleware to the traefik's docker compose config and let it handle the authentication requests.
It will require the redirect uri, client id and the client secret in the environment variables. You will also need to add the redirect uri's for each application you want to use in the zitadel configuration. Then you can use this middleware in the docker compose labels of you applications.
For this, you can use thomseddon/traefik-forward-auth container to route the authentication requests.
I know it's hard to explain over a comment so i'll try to post a video on it soon.
Hope this helps for the time being !