sleighzy
commented
3 years ago Hi @mariusrugan . I don't mind contributing if there is something I can assist with. I'm not familiar with the original oauth2-proxy. My Keycloak deployment uses username password authentication, and also provides identity brokering with Github. Should be easy enough to update my Traefik Forward Auth config to use Github directly to provide an example config for this.
i wanted an overlay on the host e.g. using a single host name - application.domain.io and not 2 : auth and application.
I went with the Auth Host Mode as I use this for numerous services, each on different subdomains, so was easier. I could try replicate your problem with the Overlay Mode if you provide me your config to see if I get similar results.
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.