apply pull-318 from upstream#26
Merged
swalker326 merged 3 commits intokagii-dev:masterfrom Apr 1, 2026
Merged
Conversation
swalker326
approved these changes
Apr 1, 2026
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
2 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.
Add
token_type: 'Bearer'to token endpoint responses for both authorization_code and refresh_token grant types to comply with RFC 6749 Section 5.1.Changes
token_type: "Bearer"to authorization_code grant response (line 883)token_type: "Bearer"to refresh_token grant response (line 951)token_typeis present in refresh token responsesRFC Compliance
Per RFC 6749 Section 5.1 (https://tools.ietf.org/html/rfc6749#section-5.1):
"The authorization server MUST include the token_type parameter in the response."
This ensures compatibility with OAuth 2.0 clients that require the
token_typeparameter, such as MCP clients using@mastra/mcp.Related: PR anomalyco#304 fixes the same issue for the implicit flow (response_type="token"). This PR addresses the authorization code flow.
Original PR: anomalyco#318
This patch was originaly done by @ygpark80