Bug fixes for security policies on API resources - #9908
Merged
Merged
Conversation
k-anshul
marked this pull request as draft
September 21, 2026 10:24
k-anshul
force-pushed
the
stricter_claims_apis
branch
from
September 22, 2026 07:03
70cdd51 to
2d2deb1
Compare
k-anshul
marked this pull request as ready for review
September 22, 2026 10:27
begelundmuller
approved these changes
Sep 22, 2026
begelundmuller
left a comment
Contributor
There was a problem hiding this comment.
Everything else looks good to me :)
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.
Immediate follow up: Opening a report through a recipient token expands transitive access, which initializes the report's resolver with the caller's claims. Resolvers that resolve security at init (e.g. metrics, metrics_sql, api) then re-expand the same transitive rules, and the expansion recurses until stack overflows.
Checklist: