Repository navigation
fix: accept the Bearer prefix on REST and gRPC tokens - #119
Merged
Merged
Conversation
Every REST handler and the gRPC config service passed the Authorization value straight to the JWT parser, so the standard "Bearer <token>" form was rejected with 401. A single bearerToken helper now strips a case-insensitive "Bearer " prefix before validation. The token blacklist key is built from the same normalized value in the auth middleware, Logout and the gRPC caller check. Otherwise a token revoked in one form would still pass in the other. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
Every REST handler and the gRPC config service passed the Authorization value straight to the JWT parser, so the standard "Bearer " form was rejected with 401. A single bearerToken helper now strips a case-insensitive "Bearer " prefix before validation.
The token blacklist key is built from the same normalized value in the auth middleware, Logout and the gRPC caller check. Otherwise a token revoked in one form would still pass in the other.
Testing
make testwith new TestBearerToken and Bearer cases in the middleware and gRPC blacklist tests — each shown to fail with the normalization removedCompatibility
Clients sending the raw token, including the web UI and fastrg_cli, are unaffected.
🤖 Generated with Claude Code