Skip to content

fix(oauth): preserve existing refresh_token when server omits it#2272

Closed
Jah-yee wants to merge 1 commit intomodelcontextprotocol:mainfrom
Jah-yee:fix/preserve-refresh-token
Closed

fix(oauth): preserve existing refresh_token when server omits it#2272
Jah-yee wants to merge 1 commit intomodelcontextprotocol:mainfrom
Jah-yee:fix/preserve-refresh-token

Conversation

@Jah-yee
Copy link
Copy Markdown

@Jah-yee Jah-yee commented Mar 11, 2026

Per RFC 6749 Section 6, the authorization server MAY issue a new refresh token. This fix preserves the existing refresh_token when the response omits it.

Per RFC 6749 Section 6, the authorization server MAY issue a new
refresh token in the refresh response. If the server does not issue
a new refresh token, the client must preserve the existing one.

This fix preserves the existing refresh_token when the OAuth server's
refresh response omits it, which is common for providers like Google,
Auth0, and Okta.

Fixes modelcontextprotocol#2270
@maxisbey maxisbey closed this Mar 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants