Livio SpringandGitHub 71fab2e574 feat: allow adding trusted domains in instance setup (#11169) ...

# Which Problems Are Solved

When running Zitadel behind a reverse proxy and especially when the API
and the login UI don't run on the same domain, Zitadel needs to be
configured to trust the corresponding domains and use them in public
responses, like email links and more.
This can be done by adding a trusted domain. However it's currently only
possible through the API and not in the instance setup process.

# How the Problems Are Solved

Added a possibility to configure multiple trusted domains in the first
instance setup process.

# Additional Changes

None

# Additional Context

- closes #11153

2026-02-23 06:06:33 +00:00

..

admin

feat(telemetry): improved instrumentation for observability (#11159)

2026-01-12 05:51:39 +00:00

build

feat(logging): add streams (#11435)

2026-02-04 11:51:43 +01:00

encryption

feat: action v2 signing (#8779)

2024-11-28 10:06:52 +00:00

hooks

feat: support whole config as env (#6336)

2024-02-16 16:04:42 +00:00

initialise

feat(logging): add streams (#11435)

2026-02-04 11:51:43 +01:00

key

feat(telemetry): improved instrumentation for observability (#11159)

2026-01-12 05:51:39 +00:00

mirror

fix(log): correct log stream in setup (#11623)

2026-02-18 06:32:03 +00:00

ready

feat(logging): add streams (#11435)

2026-02-04 11:51:43 +01:00

setup

feat: allow adding trusted domains in instance setup (#11169)

2026-02-23 06:06:33 +00:00

start

fix: correctly send links to login v2 in email notifications (#10711)

2026-02-13 13:06:56 +00:00

tls

fix: enable env vars in setup steps (and deprecate admin subcommand) (#3871)

2022-06-27 10:32:34 +00:00

defaults.yaml

chore: consistent naming for organization domain (#11356)

2026-02-18 14:46:21 +00:00

zitadel.go

feat(logging): add streams (#11435)

2026-02-04 11:51:43 +01:00