FHm, after successful login with OIDC and SAML we currently reply with a 302 (a redirect)
What I have seen work is to use Oauth-Proxy as a means to attach forward auth to OIDC compliant systems.
Other than that we are currently creating a "login api" which can respond with a 200.
@livio what do you think, could we re-use the login api for forward auth scenarios?
What I have seen work is to use Oauth-Proxy as a means to attach forward auth to OIDC compliant systems.
Other than that we are currently creating a "login api" which can respond with a 200.
@livio what do you think, could we re-use the login api for forward auth scenarios?
FNice, thank you for sharing 
FThanks, give us some time to look into this
THi @Alessandro Del Prete, thank you for your plugin !!
I'm trying to use you traefik plugin but I have only "Internal error server"
I want to protect the traefik dashboard, here my docker compose file
In Zitadel, I have configured a "web code" application, maybe it's not the right thing to do
I'm trying to use you traefik plugin but I have only "Internal error server"
I want to protect the traefik dashboard, here my docker compose file
In Zitadel, I have configured a "web code" application, maybe it's not the right thing to do
docker-compose.yml3.35KB
TI think the error is :
error.log8.23KB