Files
jcoffey-dev a579b6d04e OIDC directories: a tenant's reaches only public HTTPS addresses
An OpenID Connect directory fetches discovery, JWKS, user info and
introspection from the server. A directory a tenant manages (only when a
server administrator delegates sysDirectory*, which tenants don't have
by default) could point those at internal addresses.

For a directory with a memberTenantId, the issuer, introspection,
jwks_uri and userinfo URLs must be HTTPS and not a private IP literal,
host names are checked when they resolve, and redirects aren't followed.
Server-owned directories are unchanged. Test builds let a tenant's
directory use loopback, as push and reports do, because the harness
runs Keycloak on localhost.

is_global_ip and the public-only resolver move from common to utils,
unchanged, so the directory crate (below common) can use them; common
re-exports both.

Test: oidc::config::tenant_url_tests.

Reported privately in a security review.
2026-11-20 13:16:35 -07:00
..