mirror of
https://github.com/supermemoryai/supermemory.git
synced 2026-10-01 02:01:40 +00:00
6cae175852
Cherry-picks #1587 from @Sravanjangam, plus the OAuth half on top. When the auth backend is slow or returns a 5xx, the MCP server currently answers `invalid_token`. That is the protocol's signal to discard the credential and re-authenticate, so a brief upstream blip logs every connected client out, and `sm_` API key users have no automatic way back. These requests now return 503 with `Retry-After: 5` so clients retry instead. His change covered the API key path only. This shares one `transientAuthErrorFor` helper between `validateApiKey` and `validateOAuthToken`, so a JWKS timeout or a 5xx also returns 503 on the OAuth path that Claude, Cursor and browser clients use. Genuinely bad tokens are unaffected: bad signature, expired, and no-matching-key still resolve to 401. Verified across all seven cases. Co-Authored-By: Sravanjangam <163002695+Sravanjangam@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| auth | ||
| client | ||
| prompts | ||
| resources | ||
| tools | ||
| analytics.test.ts | ||
| analytics.ts | ||
| app-metadata.ts | ||
| container-tag.ts | ||
| format.ts | ||
| html.d.ts | ||
| index.ts | ||
| legacy-protocol-state.ts | ||
| server.ts | ||
| space-presentation.ts | ||
| space-state.ts | ||
| space.test.ts | ||
| space.ts | ||
| types.ts | ||
| widget-manifest.d.ts | ||
| widget-resource-metadata.ts | ||