Jan Larwig

@bmonteiro thank you for your contribution but we are deprecating the azure provider with v7.8 and will release the new EntraID provider: https://github.com/oauth2-proxy/oauth2-proxy/pull/2390 I hope we can get it released...

Sorry for the long long wait. Please have a look at the test failure: ``` 2024-09-30T15:56:20.5213409Z === RUN TestAllowedRequestNegateWithoutMethod/Regex_POST_api_route_denied 2024-09-30T15:56:20.5215095Z [2024/09/30 15:56:20] [oauthproxy.go:615] Error obtaining real IP for trusted IP...

Fixed the test case. The issue was that in case of a not allowed HTTP method the GetRedirect call throws an error before the default 403 status code has been...

The distroless image runs as a nonroot user. You are not allowed to create files on the root level of the filesystem. Could you try: `OAUTH2_PROXY_HTTP_ADDRESS=unix://tmp/oauth2_proxy.sock`

But why not store the cookie secret inside the config file as intended?

Hi @alexfokuk, this was actually an intended change in comparison to `docker-compose`, to truly keep everything in code. I might reconsider it but in that case a decision has to...

Hi @alexfokuk, what would be your desired behaviour for `helm compose down release-x`? A full helm uninstall of the release?

Have you tried to set the same values for the pod security context for nginx and oauth2-proxy. Something like: ```yaml securityContext: runAsUser: 1000 runAsGroup: 3000 fsGroup: 2000 ```

In Linux the user IDs aren't unique to the container. User id 0 is the root user independent of the container or the host and creating a file on a...

I'm aware of this issue but never had the time to investigate the route cause. We just deactivated the sign in page, the users don't need to know about oauth2-proxy...