Refactor AdminGuard to use JWT role claims and remove per-request user lookup - #1
Merged
Merged
Conversation
Copilot
AI
changed the title
Refactor AdminGuard to use JWT role and remove DB lookup
Refactor AdminGuard to use JWT role claims and remove per-request user lookup
Jun 18, 2026
Copilot created this pull request from a session on behalf of
d3vobed
June 18, 2026 20:34
View session
d3vobed
marked this pull request as ready for review
June 18, 2026 20:38
d3vobed
approved these changes
Jun 18, 2026
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.
AdminGuard was performing a prisma.userFindUnique on every protected request to re-check admin role, adding avoidable DB latency on hot admin paths. Since auth already establishes identity and role at token issuance, role verification can be handled from the JWT-backed request context.
Closes OrbitChainLabs#10