3 people 96b3f3dd35 fix(login): apply custom request headers from environment variable in proxy (#12144) ...

Closes #12125

# Which Problems Are Solved

The proxy middleware (proxy.ts) did not apply `CUSTOM_REQUEST_HEADERS`
to rewritten requests (/.well-known/*, /oauth/*, /oidc/*, etc.). When
`ZITADEL_API_URL` points to an internal service name, the Host header on
proxied requests remained the internal name instead of the configured
public domain, causing Errors.Instance.NotFound.

# How the Problems Are Solved

The other two outgoing request paths — the connectRPC transport and the
security-settings fetch — already applied these headers. This adds the
same applyCustomHeaders() call to the proxy path.

Co-authored-by: Ramon <[email protected]>

2026-05-12 08:34:39 +02:00

..

api

fix(oidc): use authenticated encryption for opaque tokens (#12017)

2026-04-13 10:59:50 +00:00

docs

docs: move customer portal docs to knowledge base (#12147)

2026-05-10 21:42:08 -03:00

login

fix(login): apply custom request headers from environment variable in proxy (#12144)

2026-05-12 08:34:39 +02:00