zitadel/cmd
Livio Spring 3d071fc505
feat: trusted (instance) domains (#8369)
# Which Problems Are Solved

ZITADEL currently selects the instance context based on a HTTP header
(see https://github.com/zitadel/zitadel/issues/8279#issue-2399959845 and
checks it against the list of instance domains. Let's call it instance
or API domain.
For any context based URL (e.g. OAuth, OIDC, SAML endpoints, links in
emails, ...) the requested domain (instance domain) will be used. Let's
call it the public domain.
In cases of proxied setups, all exposed domains (public domains) require
the domain to be managed as instance domain.
This can either be done using the "ExternalDomain" in the runtime config
or via system API, which requires a validation through CustomerPortal on
zitadel.cloud.

# How the Problems Are Solved

- Two new headers / header list are added:
- `InstanceHostHeaders`: an ordered list (first sent wins), which will
be used to match the instance.
(For backward compatibility: the `HTTP1HostHeader`, `HTTP2HostHeader`
and `forwarded`, `x-forwarded-for`, `x-forwarded-host` are checked
afterwards as well)
- `PublicHostHeaders`: an ordered list (first sent wins), which will be
used as public host / domain. This will be checked against a list of
trusted domains on the instance.
- The middleware intercepts all requests to the API and passes a
`DomainCtx` object with the hosts and protocol into the context
(previously only a computed `origin` was passed)
- HTTP / GRPC server do not longer try to match the headers to instances
themself, but use the passed `http.DomainContext` in their interceptors.
- The `RequestedHost` and `RequestedDomain` from authz.Instance are
removed in favor of the `http.DomainContext`
- When authenticating to or signing out from Console UI, the current
`http.DomainContext(ctx).Origin` (already checked by instance
interceptor for validity) is used to compute and dynamically add a
`redirect_uri` and `post_logout_redirect_uri`.
- Gateway passes all configured host headers (previously only did
`x-zitadel-*`)
- Admin API allows to manage trusted domain

# Additional Changes

None

# Additional Context

- part of #8279 
- open topics: 
  - "single-instance" mode
  - Console UI
2024-07-31 18:00:38 +03:00
..
admin chore: test server for direct resource access 2023-04-24 20:40:31 +03:00
build fix: allow version to be overwritten by build again (#4656) 2022-11-07 09:50:44 +00:00
encryption fix(setup): init projections (#7194) 2024-01-25 17:28:20 +01:00
hooks feat: support whole config as env (#6336) 2024-02-16 16:04:42 +00:00
initialise feat: api v2beta to api v2 (#8283) 2024-07-26 22:39:55 +02:00
key feat: api v2beta to api v2 (#8283) 2024-07-26 22:39:55 +02:00
mirror fix(mirror): read config correctly (#8330) 2024-07-18 14:00:58 +00:00
ready feat(api): feature flags (#7356) 2024-02-28 10:55:54 +02:00
setup fix(fields): add index to improve search by aggregate (#8267) 2024-07-08 15:54:19 +00:00
start feat: trusted (instance) domains (#8369) 2024-07-31 18:00:38 +03:00
tls fix: enable env vars in setup steps (and deprecate admin subcommand) (#3871) 2022-06-27 10:32:34 +00:00
defaults.yaml feat: trusted (instance) domains (#8369) 2024-07-31 18:00:38 +03:00
zitadel.go fix(mirror): read config correctly (#8330) 2024-07-18 14:00:58 +00:00