starred/aryx
1
0
Fork 0
mirror of https://github.com/davidkaya/aryx.git synced 2026-08-07 04:08:45 +02:00
Code Issues 3 Packages Projects Releases 10 Wiki Activity
479 Commits 4 Branches 30 Tags
copilot/decrypt-first-line
Commit Graph
3 Commits
Author SHA1 Message Date
David KayaandCopilot 216b17b2ac fix: add origin-only well-known URL fallback for OAuth discovery 
Some MCP servers (e.g., eschat.microsoft.com/mcp) serve their
OAuth Protected Resource Metadata at the origin without the path
suffix. Add a third candidate URL that strips the path, matching
VS Code's discovery behavior.

Tried in order:
1. RFC 9728: {origin}/.well-known/{suffix}{path}
2. Appended: {origin}{path}/.well-known/{suffix}
3. Origin-only: {origin}/.well-known/{suffix}

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
 2026-03-28 19:53:25 +01:00
David KayaandCopilot 0fd7a04a51 fix: try both RFC 9728 and appended well-known URL paths for MCP OAuth discovery 
Some MCP servers place .well-known metadata at the appended path
(e.g. /v1/.well-known/oauth-protected-resource) instead of the
RFC 9728 compliant inserted path. Now tries the RFC-compliant URL
first and falls back to the appended form.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
 2026-03-27 20:00:50 +01:00
David KayaandCopilot d73eaae30b fix: correct well-known URL construction per RFC 9728 
The .well-known/{suffix} segment was being appended to the full URL
path instead of inserted after the origin. For example:

  Wrong:   https://api.example.com/mcp/.well-known/oauth-protected-resource
  Correct: https://api.example.com/.well-known/oauth-protected-resource/mcp/

- Extract buildWellKnownUrl() helper in mcpTokenStore (Electron-free)
- Fix all 3 call sites: requiresOAuth probe, PRM discovery, auth
  server metadata
- Add 6 unit tests for URL construction with various path shapes

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
 2026-03-27 19:46:25 +01:00