Jan Larwig

Replaced by #3116 I added you as a Co-Author

https://github.com/oauth2-proxy/manifests/pull/353#issuecomment-3304122835 This will introduce an additional place to maintain the version which is already specified and updated in the Chart.yaml

Why aren't you just setting the tag / version you want in your deployment `values.yaml` ? Am I misunderstanding the problem?

> protect users from supply chain attacks that oauth-proxy might be subjects to (see recent shai hallud 2 at https://securitylabs.datadoghq.com/articles/shai-hulud-2.0-npm-worm/ ), by avoiding latest version by default (aka sensible production...

Hi @isubroto, this should definitely not be the default as it might unintentionally reveal private details people might not want to or not be allowed to share. Like details about...

Hi @shetsu01, the azure provider has been deprecated please try the new entra id provider. https://oauth2-proxy.github.io/oauth2-proxy/configuration/providers/ms_entra_id/

@shetsu01 the error message is not from oauth2-proxy. If you visit the oidc url you specific: https://icscentralalloy.b2clogin.com/19452690-09a8-47f3-89dc-335e5fe3ad21/v2.0/ You get: `The resource you are looking for has been removed, had its...

And if the oidc well-known endpoint is not reachable. Discovery won't work: Should be: https://icscentralalloy.b2clogin.com/icscentralalloy.onmicrosoft.com/b2c_1_sign_in/v2.0/.well-known/openid-configuration https://learn.microsoft.com/en-us/azure/active-directory-b2c/openid-connect#validate-the-id-token

Furthmore, you should **not** share your client id or cookie secret. Its called cookie secret for a reason ;)

I guess this might be due to the fact that we don't use the chart name `redis-ha` but instead the configured alias `redis` 🤔 Please try with `redis-ha:` in your...