Repository navigation
Release v2.49.0
Summary
Operators can now require HTTPS on every hop that carries identity or tenant context, with or without forwarded-identity signing. Turn it on for any deployment whose backends, callbacks and notifiers support TLS; the setting is off by default so existing deployments keep working.
Added
BackendTls:RequireTlsOnIdentityHopssetting that makes startup validation refuse any identity-bearing backend, callback, notifier or verifier target that is not HTTPS, with the backend TLS policy applied to it, outside local development. Loopback in local development stays allowed. (part of #265)- The backend TLS policy now also applies to capability verification when the setting is on. (part of #265)