Repository navigation
Conversation
erichare
marked this pull request as ready for review
November 2, 2026 20:00
This was referenced Nov 3, 2026
Contributor
Author
|
The November 3 alignment added deployment checks in #2634 for Authorization Bearer forwarding and database wake-up, plus permitted and denied database operations using the final identity contract, once agreed. #2654 tracks the gateway/platform and backend ownership needed for those checks. The final subject and permission contract, token lifetime, and headless launch scope remain open. Resource-server acceptance of a JWT does not establish that the backend authorizes its identity correctly. Existing user-token behavior also needs to remain intact. These are integration dependencies alongside the local verification already recorded in this PR. |
Contributor
📈 Unit Test Coverage Delta vs Main Branch
|
Contributor
Unit Test Coverage Report
|
Contributor
📉 Integration Test Coverage Delta vs Main Branch (hcd-it)
|
Contributor
Integration Test Coverage Report (hcd-it)
|
Contributor
📉 Integration Test Coverage Delta vs Main Branch (dse69-it)
|
Contributor
erichare
force-pushed
the
fix/mcp-oauth-integration
branch
from
November 5, 2026 19:28
c805b3a to
939ed32
Compare
This was referenced Nov 5, 2026
erichare
changed the base branch from
fix/mcp-request-isolation
to
feat/mcp-protocol-2026-07-28
November 5, 2026 19:29
A deployment that serves one public host per database can now set stargate.mcp.auth.public-host-suffix in place of the fixed public base URL. The protected resource metadata, the 401 challenge and the required aud claim are then built from the host of each request, so a token issued for one database is rejected on another. A host outside the suffix receives 401 without a challenge. Bearer authentication now also requires mp.jwt.token.header to be Authorization. Without a static audience list the built-in JWT mechanism accepted a token from a cookie on REST paths with no audience check.
An authorization server can list one resource per granted database in aud. Check that such a token works on each listed database host and is still challenged on a host it does not list.
erichare
force-pushed
the
fix/mcp-oauth-integration
branch
from
November 19, 2026 05:41
0f1f14b to
b50eede
Compare
…ation # Conflicts: # src/test/java/io/stargate/sgv2/jsonapi/api/v1/mcp/McpResourceTest.java
This was referenced Nov 19, 2026
# Conflicts: # src/main/java/io/stargate/sgv2/jsonapi/api/v1/mcp/McpEndpointConfigSourceFactory.java # src/main/java/io/stargate/sgv2/jsonapi/api/v1/mcp/McpOriginFilter.java
This branch has not been deployed
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.
What this PR does:
Adds opt-in OAuth authentication and public discovery for MCP. Tool calls check the scope and database audience. Ordinary REST keeps its existing token headers. OAuth requires a JWT verifier at startup. Missing scope and database permission denials return distinct HTTP 403 challenges. Embedding and reranking use separate credentials.
Which issue(s) this PR fixes:
Part of #2642 and #2643. End-to-end OAuth is tracked in #2654. Builds on #2659. Full stack.
Verification
4,226 Java tests and 14 Python smoke-script tests passed on
4e44ab7d9with JDK 21. Both legacy REST headers worked with strict inclusive authentication. With the verifier excluded, OAuth refused to start and legacy MCP still worked. Supported-client sign-in and public Astra authorization remain open in #2633 and #2634. Unit, DSE 6.9, and HCD CI passed.Verifier startup check
The first command passed both legacy headers. The second stopped at startup with the expected message naming the required verifier.
Checklist