Replies: 1 comment
-
|
Found a far from ideal workaround of using |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I'm willing to deploy Zitadel combined with oauth2-proxy so that my backend has almost no concerns when it comes to authenticating the requests.
The issue I'm facing is that since SSL termination is being handled outside Zitadel (as expected) and
oauth2-proxyis reaching to zitadel via the service mesh it only sees zitadel HTTP port but when trying to do the OIDC discovery Zitadel responds with a HTTPS header since it thinks everyone is reaching to it from the external world and hence via HTTPS.Below is the error message I'm getting from
oauth2-proxy:Is there any configuration option I can set on zitadel to select between http and https on a per-host basis?
Beta Was this translation helpful? Give feedback.
All reactions