Revision 1 · · Our best guess
Scoped agent token audience enforcement is now always on: the `agent-token-audience-enforcement` flag is removed, `FF_DISABLE=agent-token-audience-enforcement` does nothing, and any scoped agent or on-behalf-of token used outside its scope is rejected with `403 invalid_target`. Clients must request a `resource` that matches every server they use the token on, or request a token without `resource`.
machine summarizer