Finding / openhands

2026-10-24-openhands-mcp-oauth-installation-and-refresh-improve-while-acp-credential-forwarding-remains-unrelea

MCP OAuth installation and refresh improve, while ACP credential forwarding remains unreleased. Canvas can install library MCP servers that require OAuth without another auth mechanism. SDK registration chooses an authentication method supported by the server and avoids duplicate Basic credentials. A conversation’s failed refresh no longer destroys its stored OAuth credentials. Enterprise resolves saved-secret references in the connection-test path, which then rejects OAuth-authenticated probes. The tool-call route expands references only when server.oauth_auth is None, avoiding copying OAuth client secrets into refreshed state. These are not general OAuth-server probe support. The separate change forwarding OAuth2 MCP credentials into ACP agents is only on main.

Channel: tagged-release (installation and refresh); main-unreleased (ACP forwarding). Half: both. Date: 2026-10-22 (Canvas v1.31.0 and SDK v1.58.0); 2026-10-23 (Enterprise 1.78.0 and ACP main change).

Operator consequence: Upgrade the matched stable bundle for installation and refresh failures before manually recreating credentials. Test the actual MCP operation, not only the connection indicator. Operators using an ACP engine must not assume stable 1.58.1 includes the forwarding repair. This reduces auth glue and repeated consent work, while backend and engine compatibility still determine which credential path is in use.

Receipt

Finding metadata

Run: 2026-10-24-weekly-digest-2026-10-13_2026-10-24-frontier-v0

Finding ID: 2026-10-24-openhands-mcp-oauth-installation-and-refresh-improve-while-acp-credential-forwarding-remains-unrelea

Profile citations

  • OpenHands / claim / mcp-oauth-and-unreleased-acp-forwarding
  • OpenHands / posture / governance

Source links

Primary links, including exact changelog lines when available.