client_id-confusion :/ ... #4340
Unanswered
flypenguin
asked this question in
Q&A
Replies: 0 comments
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.
-
Hi fellow Dexians,
First of all: I think my use case is "valid", as in "supported and possible – if I am in fact wrong about this please tell me.
The setup
So I am trying to configure Dex in an authentication chain on Kubernetes as follows:
(I have a repository with a configured playground here, simply go
make prepare ; make deployand you should be set up if you're interested).Current situation
traefik-oidcNow I have deployed a simple nginx, which I intend to authenticate using Traefik OIDC. When I go to the web page, this happens:
Not Found | Invalid client_id ("traefik-oidc")."I would have expected in my little perfect fantasy world that now I simply authenticate against one of those Authelia instances, and am being redirected back to my nginx page. And to me it seems perfectly straightforward that "Traefik <-> Dex", "Dex <-> Authelia I", and "Dex <-> Authelia II" have separate sets of client IDs and secrets, so I really am lost about how to interpret this error message.
This is, obviously, not the case. And I hope I'm doing something wrong, instead of expecting something "not possible", and in each of both cases, I am pretty desperate for any help now :/ ...
The config files
... for completeness
Details
GitHub permalink
Helm values file for Dex
Details
GitHub permalink
Helm values for "authelia-local" (one of the two)
Details
GitHub permalink
Traefik OIDC plugin config
Details
GitHub permalink
Helm values for Traefik
Beta Was this translation helpful? Give feedback.
All reactions