chore(backend): verify requireAuth rejects tokens with missing subject/user id#293
Merged
greatest0fallt1me merged 2 commits intoCalloraOrg:mainfrom Apr 25, 2026
Conversation
Contributor
Author
|
Hello @maintainer, Kindly review my PR and merge so the issue can be closed |
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.
Closes #217
This Pull Request addresses issue #217 by hardening the
requireAuthmiddleware to ensure it strictly validates the presence of a user identifier in JWT tokens. It also resolves a critical syntax bug in the global error handler that was blocking proper error reporting.Changes
src/middleware/requireAuth.ts:userIdandsub(standard JWT subject) claims.userIdis prioritized, butsubis accepted ifuserIdis missing.401 Unauthorized(MISSING_CLAIMS) if neither claim is a valid, non-empty string.src/middleware/errorHandler.ts:SyntaxErrorcaused by a duplicate declaration of themessagevariable.undefinedreference toisKnownErrorby replacing it with the correctisAppError(err)check.tests/integration/auth.test.ts:requireAuthmiddleware.userId, and emptysub.userIdand validsubfallback.Security & Data Integrity
The updated logic ensures that authorization is never granted to tokens that do not explicitly identify a subject. By supporting the standard
subclaim alongside the internaluserId, we improve compatibility with standard JWT issuers while maintaining strict security boundaries.Test Results Summary