This repository was archived by the owner on Jun 23, 2026. It is now read-only.
Skips token validation on auth routes - #46
Merged
Merged
Conversation
Exempts login, token refresh, and logout endpoints from standard access token validation. These routes either don't carry an access token or handle session management in a way that bypasses this specific validation.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The token validation middleware now bypasses token extraction and claim setting for critical authentication endpoints. This ensures that routes such as
/api/user/login,/api/user/refresh, and/api/user/logoutcan operate correctly without requiring a valid access token upfront.This adjustment prevents premature unauthorized errors, allowing the respective handlers to manage initial authentication, token renewal, or token invalidation processes as intended.