feat(seer): Add principal-aware agent token minting - #121040
Open
gricha wants to merge 1 commit into
Open
Conversation
Restrict agent capability-token minting to real user principals and reject Sentry App proxy users. Add typed principal decoding behind a rollout-compatible numeric subject so older instances continue accepting newly minted tokens.
gricha
marked this pull request as ready for review
August 2, 2026 18:13
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.
Restrict Seer agent capability-token minting to real user principals. Sentry App installation credentials authenticate through proxy users, so the mint endpoint now classifies that provenance and rejects those integrations instead of treating them as human organization members. User sessions, personal tokens, and delegated user OAuth continue to mint within their existing scope ceiling.
This also introduces a typed principal representation and versioned subject decoding for future principal types. The first rollout intentionally continues emitting the existing numeric JWT
sub, because older Sentry instances still parse it as an integer. Typed subjects are already accepted and can be enabled in a follow-up after this decoder is deployed everywhere and the five-minute token lifetime has elapsed.Review focus is the credential classification boundary and the decoder-first rollout compatibility.