Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

auth: refresh_token() always sends `scope`, so refresh fails against Salesforce ("scope parameter not supported")

未關閉
  • 哪裡不對？
#1,408 1 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 3 天內回覆

@gocamille 已經在處理了。

開始於 2026年10月29日。

評估

這個 Issue 還沒有評估資料。

描述

bug P1 ready for work T-security T-transport

Summary

AuthorizationManager::refresh_token() always adds the stored granted_scopes (plus offline_access when advertised) to the refresh request as scope. Salesforce's token endpoint rejects any refresh request that includes scope:

400 {"error":"invalid_request","error_description":"scope parameter not supported"}

So every refresh fails against a Salesforce-hosted MCP server, and the user has to go through the full authorization flow again each time the access token expires. Clients built on rmcp, including Codex, can't do anything about it, because there's no way to leave scope out of the refresh request.

Where it happens

crates/rmcp/src/transport/auth.rs on main (9e0783d):

let mut refresh_scopes = stored_credentials.granted_scopes.clone();
self.add_offline_access_if_supported(&mut refresh_scopes);
let requested_scopes = refresh_scopes.clone();
for scope in refresh_scopes {
    refresh_request = refresh_request.add_scope(Scope::new(scope));
}

Clearing the stored granted_scopes doesn't help either. Salesforce returns scope in every token response ("scope": "refresh_token mcp_api"), and resolve_granted_scopes stores it again, so the next refresh sends scope once more.

Reproduction

Server: a Salesforce Hosted MCP server (https://api.salesforce.com/platform/mcp/v1/...) with a pre-registered public client (PKCE, no secret). The External Client App has "Require secret for Refresh Token Flow" turned off.

Direct calls to the org's /services/oauth2/token with the same refresh token:

Request Result
grant_type=refresh_token&client_id=…&refresh_token=…&scope=mcp_api refresh_token 400 invalid_request: scope parameter not supported
grant_type=refresh_token&client_id=…&refresh_token=… 200, new access token; response includes "scope":"refresh_token mcp_api"

The same failure through Codex CLI 0.161.0 (rmcp 3.5.1, rev 98a5478), with RUST_LOG=codex_rmcp_client=debug,rmcp=debug:

refresh_transaction{... refresh_reason="expiry"}: rmcp::transport::auth: refresh token present, attempting refresh
WARN ... MCP OAuth provider refresh failed error=OAuth token refresh failed: Server returned error response: invalid_request: scope parameter not supported
WARN ... MCP OAuth access token is expired and refresh failed; reauthorization required

For comparison, the MCP TypeScript SDK's refreshAuthorization sends no scope, only resource, and refreshes silently against the same Salesforce server and client. That also shows Salesforce accepts the RFC 8707 resource parameter that rmcp now adds to refresh requests. Only scope is the problem.

Why this should be configurable

  • RFC 6749 §6 makes scope OPTIONAL on refresh. If it's omitted, the server treats the request as asking for the originally granted scope.
  • Salesforce's OAuth 2.0 Refresh Token Flow documents grant_type, refresh_token, client_id, client_secret, client_assertion, client_assertion_type and format as the request parameters. scope isn't one of them.
  • Some providers do need scope on refresh. Microsoft Entra is one (see mcp-remote#357). So "never send scope" isn't a safe default.

Proposed fix

Either of these would work. They aren't mutually exclusive:

  1. Retry without scope: if the refresh fails with invalid_request (or invalid_scope) and scope was sent, retry once without it. This works without any client changes and doesn't change behavior for providers that accept scope.
  2. Opt-out: a setting on AuthorizationManager / OAuthState, for example omit_scope_on_refresh: bool, that clients can expose in their config.

ToolHive hit the same Salesforce error and fixed it with an opt-out: stacklok/toolhive#6830 (PR #6832).

Related

  • #1330 / #1331: #1330 is about refresh requesting offline_access that was never granted. PR #1331 refreshes with the granted scopes, so it still sends scope and won't fix Salesforce. A fix for this issue should cover the case where the server returns scope in the token response but won't accept it on refresh.
  • openai/codex#58103: the downstream Codex issue.
主要語言
Rust
星號
4.1k
分支
680
平均合併
3 天 23 小時
30 天內合併 PR
34

環境準備

在 Codespaces 中開啟

在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

modelcontextprotocol/rust-sdk 的其他 Issue

查看 modelcontextprotocol/rust-sdk 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。