Jan Larwig

@mmmommm I don't think the snippet is necessary. The official ingress-controller example for using oauth2-proxy doesn't include anything of that sort either. https://kubernetes.github.io/ingress-nginx/examples/auth/oauth-external-auth/ I'll have to do some testing to...

Regarding your setup, which of the following are you trying to accomplish: 1. upstream behind oauth2-proxy ``` user -> nginx -> oauth2-proxy -> upstream ``` 2. upstream behind nginx with...

Furthermore you cannot protect two upstreams using the same path. https://oauth2-proxy.github.io/oauth2-proxy/docs/next/configuration/overview#upstreams-configuration > Multiple upstreams can either be configured by supplying a comma separated list to the --upstream parameter, supplying the...

Hi @David-Igou, this is unfortunately a known issue. We will have to update the CHANGELOG and maybe release a bug release. You have to add the full scope to your...

Root cause: https://github.com/oauth2-proxy/oauth2-proxy/pull/2196

On top you can just switch to KeyDB which is a multi threaded fork of Redis and the redis client library in go should be fully compatible with it.

Valkey is the official replacement sponsored by the linux foundation but KeyDB is actually more performant

Hi @rockhouse, try to completely remove the scope flag.

You only use the flags mentioned in your config above? No other settings via environment variables?

We had similar requests in the past. This to me sounes like feature creep and we most likely aren't going to support this. Use existing solutions dedicated for providing static...