Replies: 1 comment
-
Thanks for the kind words @divStar ❤. I'm glad the plugin helps you. Yes, using separate middlewares per client or application is exactly the way to go. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Daniel!
As mentioned elsewhere, thank you very much for making this awesome plugin!
I'd like to ask if it's possible to use it with multiple clientIDs.
Basically I have e.g. the Traefik dashboard, PiHole, whoami and possibly other applications, that I would like to protect using your plugin. I created separate projects / applications in Zitadel and got their clientIDs.
I thought, that I could use
traefik.http.middlewares.oidc-auth.plugin.traefik-oidc-traefik-dashboard.Provider.ClientIdEnv
for this very reason and just specify a variable, that I would change in eachdocker-compose.yml
file accordingly (all the other settings can stay the way they are).This didn't work.
I then thought I could have multiple instances of this plugin, but this didn't work either.
Edit: I probably changed the wrong name in
- "traefik.http.middlewares.oidc-auth.plugin.traefik-oidc-auth.Provider.ClientId=320323122081366029"
I should have changed
oidc-auth
to a per-clientId name while I changed the name of the plugin (traefik-oidc-auth
) 🤦♂️ .I probably could have one project and multiple roles, but from what I understood: if the user has any of the asserted roles, he will be permitted to use any protected service, right?
What's the best way to get this done or is it not (yet?) possible?
TL;DR: creating a middleware per clientID works. Sorry for the hassle.
Beta Was this translation helpful? Give feedback.
All reactions