Use canonical role casing for login tokens#3340
Open
LikeACloud7 wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
/claim #743
Closes #3338
Summary
CLIENTrole claim used by the PrismaUserRoleenum.Validation
node --check apps/api/src/services/authService.jsnode --check apps/api/src/tests/authService.test.jsnode --test apps/api/src/tests/authService.test.jsnode --test apps/api/src/tests/*.test.jsgit diff --checkDemo evidence: the focused Node test exercises the login flow, decodes the issued JWT, and verifies the canonical role claim.
AI assistance disclosure: this PR was prepared with Codex assistance and manually scoped to the login-token role casing issue.