Patch Changes
-
#415
6b50ae3Thanks @mattzcarey! - A refresh of a grant bound to a resource the server no longer hosts now fails withinvalid_grant, even when the request names that resource. MCP clients repeat their grant'sresourceon every refresh, so after a server dropped a resource (an/sseendpoint, or the bare origin a 0.x server advertised at its root metadata URL), those refreshes gotinvalid_target. The MCP SDKs throw oninvalid_target, so the user stayed stuck until they removed the server. Oninvalid_grantthey discard their tokens and sign the user in again. The description now says so: "The authorization grant is bound to a resource this server no longer serves. Authorize again."A refresh of a valid grant that names a resource the server doesn't host still gets
invalid_target. The resource is still checked before thetokenExchangeCallbackruns or anything is written.