[Access] Document service token auth and device auth limitation for MCP portals#31008
Draft
kennyj42 wants to merge 1 commit into
Draft
[Access] Document service token auth and device auth limitation for MCP portals#31008kennyj42 wants to merge 1 commit into
kennyj42 wants to merge 1 commit into
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
3 participants
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.
What this PR does
Why
Service tokens: The gateway code supports service token auth with specific routing behavior (bypasses OAuth provider, routes directly to MCP DO, uses
svc:<id>user ID format). This is useful for CI/CD pipelines and automated agents but was completely undocumented.Device auth: A customer asked about this at RSA. Internal SEs confirmed the option does not show up for MCP portals. Without this note, customers will search for a feature that does not exist.