feat(auth): support returning extra fields from token exchange#700
Open
glicht wants to merge 2 commits intomodelcontextprotocol:mainfrom
Open
feat(auth): support returning extra fields from token exchange#700glicht wants to merge 2 commits intomodelcontextprotocol:mainfrom
glicht wants to merge 2 commits intomodelcontextprotocol:mainfrom
Conversation
…token generation exchange_code_for_token and refresh_token now return a StandardTokenResponse which includes any additionalfields which might have been sent by the vendor BREAKING CHANGE: Return type of exchange_code_for_token and refresh_token has changed and may require code changes.
github-actions
bot
added
T-core
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
1 participant
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.
Added
VendorExtraTokenFieldsto be used withStandardTokenResponseto expose any vendor-specific fields the authorization server may have included in the JSON response body for token generation.exchange_code_for_tokenandrefresh_tokennow return aStandardTokenResponsewhich includes any additional fields which might have been sent by the authorization server.Motivation and Context
Some vendors return additional fields as part of the token API. I've experienced this specifically with HubSpot MCP Server which includes additional fields in it's response. It wasn't possible to access these fields when calling
exchange_code_for_token.How Has This Been Tested?
Tested locally with HubSpot's MCP server.
Breaking Changes
Return type of
exchange_code_for_tokenandrefresh_tokenhas changed and may require code changes.Types of changes
Checklist
Additional context