Repository navigation
Release v2.50.0
Summary
Operators can now require every token from an external issuer to carry a verified tenant. Turn it on when external issuers sign tokens for more than one tenant; the setting is off by default so existing deployments keep working.
Added
Authentication:ExternalTokenTenantBindingsetting. When enabled, a token from an external issuer is accepted only if it carries exactly one configured tenant claim (optionally mapped to a tenant through issuer-scoped mappings). A token whose tenant differs from the addressed tenant is refused with 403. Headers, routes and tool arguments only select a target and never constrain the credential. Startup validation rejects incomplete settings, and a startup warning appears when external bearer tokens are configured without it. (part of #270)