sleighzy / k3s-traefik-forward-auth-openid-connect Goto Github PK

Hi!

would like to hear your thoughts on managing together a fork from this config but operating with oauth & github (like the original oauth2-proxy).
I've managed to get it up and running, with a minor imperfection from my end - i wanted an overlay on the host e.g. using a single host name - application.domain.io and not 2 : auth and application. However cannot get it going (cannot manage to get 2 routes up : one going into middleware one going into the service - even by digging very deep into traefik-forward-auth issues. even his official examples are based on this 2 tiered system.
however i like it, since it's just a service whereas i am used to it in a swarm - i'm an early adopter of the funkypenguin system - there is a sidecar container to each stack.

Hi, thanks a lot for sharing your code. According to your source, I implemented it, but get back a response from Keycloak:
We are sorry... Invalid parameter: redirect_uri

Could you guide me, how a redirect_uri could look like?
I tested like
http://traefik-forward-auth.default:4181
(yes, my namespace is default for now, traefik, keycloak and your container are all inside one kubernetes), but was not successfull.
I also tried an external access https://auth.mydomain with the same result. Really would appreciate, if you can guide me, how the redirect_uri should look like.
Thanks,
Wolfram