Repository navigation
fix(authz): prove query fields within enforced tenant scopes - #257
Merged
Merged
Conversation
rrrodzilla
marked this pull request as ready for review
October 11, 2026 19:52
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.
A tenant-keyed custom forbid currently blocks filters and sorts on every
@field_accessfield, including requests from an allowed tenant or an exempt platform administrator. Bind the field proof to the complete tenant scope enforced by the storage query, and require the original Cedar policy set to allow field reads for every candidate tenant.Share the captured scope between authorization and filter injection across REST, JSON queries, GraphQL, and export acceptance/execution. Keep admin and disabled-tenancy queries unscoped. Recognize ordered Boolean conditions that prove a policy independent of records for the caller, preserving evaluation errors and optional-attribute guards. Keep generated-policy integrity checks, concrete resource ancestry, public APIs, and dependency features unchanged.
Prepare CLI 0.52.3 and runtime 0.50.2 as patch releases for existing query behavior.
Fixes #256.
Validation:
test-surrealdb,graphqlpassed with zero warnings (-D warnings).