Frontend using http, even though backend is configured with tlsMode external
Original message was deleted
FCan you share your how you deployed Zitadel?
Maybe its also something on the annotation of the nginx
Maybe its also something on the annotation of the nginx
FHm usually it always comes down to either proxy or Zitadel config
FHow does your deployment look like
FOk, can you give this config for nginx a stab?
https://github.com/zitadel/zitadel/issues/4455#issuecomment-1258445815
https://github.com/zitadel/zitadel/issues/4455#issuecomment-1258445815
GitHub
Hello, I am evaluating Zitadel as an IdP for our product. And we want also have a look at it, running in our own infrastructure to test and analyze a bit. Describe the bug We have a kubernetes Clus...
FWe have seen both with Zitadel, L7 Lb and L4 LB + Ingress. The crucial part is that somehow the host header is propagated.
FConsole will get its info from the environments.json loaded from the Zitadel API.
This will render with the config in mind. So ExternalSecure is mostly important to have the redirectURI built correctly, otherwise the oidc flow can not work
This will render with the config in mind. So ExternalSecure is mostly important to have the redirectURI built correctly, otherwise the oidc flow can not work
FWhat is the
tlsMode? Should be external as wellFHm, these look actually good
Can you share your environment.json or a URL I can test is myself?
(Can be a DM)
Can you share your environment.json or a URL I can test is myself?
(Can be a DM)
FAh good, with that we have a lead... this looks like protocol missmatch on the upstream.
I.e. your proxy calls with http instead of https
I.e. your proxy calls with http instead of https
FThe issuer gets rendered out of the host header that arrives at Zitadel (to allow for multidomain cases).
FHm, that sounds odd.
Which versions are we talking here?
Which versions are we talking here?
FLet me check if we touched that, but of the top of my head I do not a change on that 