You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To support operating in environments that enforce/require client TLS certificates it would be helpful to support mTLS configurability between the proxy and the OIDC issuer.
This would involving adding new command line arguments to specify a TLS certificate and private key. For example, something like:
flagset.StringVar(&o.Auth.Authentication.OIDC.ClientCertFile, "oidc-client-cert-file", "", "If set, the client certificate will be used to authenticate the proxy to the OIDC server. Requires --oidc-client-key-file to be set, too.")
flagset.StringVar(&o.Auth.Authentication.OIDC.ClientKeyFile, "oidc-client-key-file", "", "The key matching the certificate from --oidc-client-cert-file. If set, requires --oidc-client-cert-file to be set, too.")
The text was updated successfully, but these errors were encountered:
I've got a PR ready to go for this. Waiting for #323 to merge before submitting it since there is a dependency on that PR to enable testing the functionality.
To support operating in environments that enforce/require client TLS certificates it would be helpful to support mTLS configurability between the proxy and the OIDC issuer.
This would involving adding new command line arguments to specify a TLS certificate and private key. For example, something like:
The text was updated successfully, but these errors were encountered: