Joseph Petersen

I might end up writing my own validate_token 😓

well, clearly azure ad's oidc is not compliant 😓 Not sure whether it is something we want to fix but again doing it in the library might help other users.

@dmeremyanin I think a missing case for this is when `UseForwardedHeaders` and `UseProxyProtocol` is enabled. In the case of the Forwarded For header is missing it resolves to the intermediate...

This is generated, so not the correct place to fix it.

For anyone still struggling with this, the problem is actually this line. https://github.com/kubernetes/ingress-nginx/blob/fb745c1e6d0b11091abc23e66793e09e58a91f81/rootfs/etc/nginx/lua/lua_ingress.lua#L122 Which on every location override the pass_access_schema back to schema. So whatever logic you attempt to use...

How about we use enUS as locale until we have proper fix? At least so we can use winget on Core? I think that provides a better experience than not...

@strongjz I have a very similar case. I want to support both NLB using (proxy protocol) and ALB using client port preservation, but use-forwarded-headers behavior is odd ie. it removes...

@dmeremyanin I not entirely sure how #12768 fixes customizing X-Forwarded-For? I cannot get it to include the port number and even with proxy-protocol. Even when I use `forwarded-for-header: "CloudFront-Viewer-Address"` it...

The issue is about customizing X-Forwarded-For which I think would include getting the remote port. I have created a commit but have had trouble figuring out how to build an...

Would be very interested in how use this feature from nginx 1.25 via ingress nginx helm chart 👏