ref(seer): Reapply JWT proxy_headers for Seer callbacks#113499
Merged
Conversation
github-actions
Bot
added
the
Scope: Backend
gricha
force-pushed
the
gricha/fix/restore-jwt-proxy-headers
branch
from
68a0f8c to
6c3de87
Compare
gricha
force-pushed
the
gricha/fix/restore-jwt-proxy-headers
branch
from
73ac432 to
3da5980
Compare
azulus
approved these changes
Apr 21, 2026
gricha
added a commit
that referenced
this pull request
Apr 22, 2026
Remove the legacy raw JSON plus `X-Viewer-Context-Signature` fallback from Sentry and only accept JWT-based `X-Viewer-Context` headers. This is the Sentry-side cleanup after restoring JWT proxy-header propagation. With the JWT path in place, keeping the legacy branch only preserves dead parsing logic in the viewer-context middleware and auth layer. This also updates the Sentry tests that were still constructing the two-header format so they exercise the current JWT contract instead. This PR is stacked on top of #113499. It should land after getsentry/seer#5902. --------- Co-authored-by: OpenAI Codex <noreply@openai.com>
3 tasks
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
2 participants
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.
Reapply the JWT
X-Viewer-Contextproxy header format for Seer callbackrequests.
This restores the earlier change that switched Code Mode proxy headers from the
legacy JSON+HMAC pair to the single JWT
X-Viewer-Contextheader. The revertwas used as a mitigation while we investigated auth failures in production.
I want to keep this change ready to land again once the infrastructure-side
routing/header issue is resolved. Restoring it here makes the intended callback
auth format explicit again and keeps the tests aligned with the JWT path.
This only reapplies the previous behavior; it does not attempt to address the
infra issue in this PR.