Expand vMCP two-boundary auth diagram and descriptions#681
Open
Expand vMCP two-boundary auth diagram and descriptions#681
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the vMCP authentication documentation to make the two-boundary model more concrete by expanding the diagram and clarifying the incoming/outgoing boundary descriptions.
Changes:
- Expands the Mermaid diagram to show token validation → Cedar policy authorization → backend proxy as distinct internal steps within vMCP.
- Clarifies what token validation entails (JWT checks vs opaque token introspection) and that this occurs in-process in
vmcp. - Simplifies Boundary 2 text to point readers to the “Outgoing authentication” section for supported strategies.
- Show token validation, Cedar policy authz, and backend proxy as distinct steps inside the vMCP box - Clarify Boundary 1 covers issuer, audience, expiry, and signature (JWT) or introspection (opaque tokens) - Note that audience must be explicitly configured for vMCP, unlike plain MCPServer deployments - Replace incomplete outgoing strategy list with a link to the Outgoing authentication section Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Line 22: add signature/introspection to diagram token validation node to match prose description of JWT and opaque token paths - Line 48: replace inaccurate blanket audience requirement with accurate distinction: required for oidcConfigRef, optional for inline OIDC Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Description
Addresses user feedback that the two-boundary authentication model diagram was too abstract. Specifically:
vmcpprocess, unlike a plain MCPServer deployment where a separate ToolHive proxy handles authType of change
Related issues/PRs
Screenshots
Submitter checklist
Content and formatting