DRAFT: FEAT: enables oauth proxy capability #1075
Draft
+1,388
−23
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Enables a pass through OAuth server to mask upstream auth server lacking DCR.
Motivation and Context
I sometimes want to auth my mcp server against authentication severs that do not have DCR enabled.
How Has This Been Tested?
I have tested this with my cursor client and the example MCP server included. I have also run the unit tests and made sure that more were added for this new functionality.
Breaking Changes
None
Types of changes
Checklist
Additional context
This proxy server simply intercepts part of the 3LO oauth handshake. Specifically the /register portion all tokens are still minted and checked by the upstream server.