Uh oh!
There was an error while loading. Please reload this page.
docs(changelog): correct the no-type agent behaviour - #765
Merged
Conversation
The 2.4.0 entry still claimed a model without `type agent` keeps pre-2.4.0 behaviour byte-for-byte. e70c0b7 changed that: the check now denies, with --fga-allow-unconstrained-agents as the migration opt-out. The flag shipped with no changelog entry at all. Both states still meter as outcome="not_enforced", so a reader hitting that metric was being told their agents run unconstrained when in fact their delegated calls are being denied — opposite diagnosis, opposite remedy. Refs #764
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
One sentence in the 2.4.0 changelog entry for agent-identity intersection.
Was: "Deployments without the type keep today's behaviour byte-for-byte and are counted as
outcome="not_enforced""Is: a model with no
type agentnow denies delegated checks.--fga-allow-unconstrained-agentsrestores the user-alone behaviour for migration. Both states meter asnot_enforcedand log at warn.Why
e70c0b77(fail closed on unevaluable agent constraint) changed the default from authorize-as-user-alone to deny, and added--fga-allow-unconstrained-agents. It updated the code, the tests andexamples/with-agent-permissions, but not the changelog — the flag has no changelog entry anywhere.That left the release notes asserting the opposite of what ships. Concretely: an operator who sees
authorizer_fga_delegated_checks_total{outcome="not_enforced"}climbing reads the changelog, concludes their agents are silently over-privileged, and starts an exposure investigation — when the real situation is that their delegated calls are being denied and their integration is broken. Opposite diagnosis, opposite remedy.Scope
Documentation only, no code. The same stale claim in the docs site is fixed in authorizerdev/docs#87.
Refs #764