fix(issuer): add token_type to authorization code flow token responses#318
Open
ygpark80 wants to merge 1 commit intoanomalyco:masterfrom
Open
fix(issuer): add token_type to authorization code flow token responses#318ygpark80 wants to merge 1 commit intoanomalyco:masterfrom
ygpark80 wants to merge 1 commit intoanomalyco:masterfrom
Conversation
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. - Add token_type to authorization_code grant response (line 883) - Add token_type to refresh_token grant response (line 951) - Update tests to verify token_type is present in refresh token responses 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."
swalker326
approved these changes
Dec 19, 2025
andrewmd5
added a commit
to 6over3/openauth
that referenced
this pull request
Apr 26, 2026
Cherry-picks from anomalyco/openauth open PRs: - anomalyco#305 spec-compliant redirect_uri (require `allow`, RFC 9700 §4.1) - anomalyco#309 client-side JWT audience validation (RFC 7519 §4.1.3) - anomalyco#318 token_type=Bearer on token responses - anomalyco#304 implicit-flow no refresh token (RFC 6749 §4.2.2) - anomalyco#258 iat claim (deterministic across reuse interval) - anomalyco#323 fix Cloudflare KV runaway key creation under eventual consistency - anomalyco#315 loosen CloudflareStorageOptions to structural KV shape - anomalyco#319 refresh callback hook - anomalyco#156 OAuth2 scope (authorize, token, well-known, JWT claim) - anomalyco#236 basePath option - anomalyco#278 allowRegistration / userExists / allowClaims - anomalyco#221 configurable Select copy - anomalyco#310 anomalyco#308 code UI resend action + sendCode types - anomalyco#325 example actions: keep session when access token still valid - anomalyco#317 add MIT license to package.json Bump 0.3.12 -> 0.4.0 (breaking: `allow` is now required).
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):
This ensures compatibility with OAuth 2.0 clients that require the
token_typeparameter, such as MCP clients using@mastra/mcp.Related: PR #304 fixes the same issue for the implicit flow (response_type="token"). This PR addresses the authorization code flow.