Repository navigation
Document fail-closed rejection of empty permission route segments - #462
Merged
Merged
Conversation
#372 made any permission route with an empty path segment (for example kv://#read, a trailing slash, or //) invalid, and one invalid grant fails the whole permission claim and with it token authentication. That is the intended fail-closed behaviour, but neither the grammar rule nor the failure mode was documented. Document both in the client permission spec, the Auth0 troubleshooting guide, and the MCP OAuth provider guide, and pin whole-claim rejection (with no fallback to a lower-priority source) in a claims test.
smiggleworth
commented
Oct 10, 2026
smiggleworth
left a comment
Contributor
Author
There was a problem hiding this comment.
Adversarial source review of 9f40c8b. Reviewed fail-closed permission normalization and source precedence; docs match authentication path. Integration with the latest develop and fresh hosted checks remain required before merge.
…ep-docs462-20261011
…ep-docs462-20261011
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Documents the existing permission parser contract: empty route path segments invalidate a grant, and one invalid grant in the selected permission source rejects that whole claim. Authentication does not keep the other grants or fall back to a lower-priority source. Unused lower-priority sources are not parsed.
Client/Auth0 guidance describes refused CONNECT authentication; MCP OAuth guidance describes invalid fitz_permissions provisioning as 403 insufficient_scope. Explicit malformed path examples avoid confusion with the scheme separator.
A regression mixes valid grants with kv://#read and a valid lower-priority scope, then requires normalization to fail. There are no production code changes.
Validation
AI assistance: Codex clarified documentation and independently reviewed existing behavior.
Fixes #430