feat: Allow verifyToken to throw errors#63
Merged
quuu merged 1 commit intovercel:mainfrom Jul 8, 2025
Merged
Conversation
Collaborator
dvoytenko
approved these changes
Jun 21, 2025
Member
|
@quuu this looks good |
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
3 participants
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.
It would be great if verifyToken could throw an error directly to trigger re-authentication. I imagine people will be doing things like validating JWT signatures there (at least - that’s what I’m doing!).
If my validation method throws an error, it triggers the Unexpected error authenticating bearer token block here which means application code needs to catch its own errors and then either return undefined or re-throw as the proper underlying mcp auth error class, both of which are rather annoying.