Repository navigation
chore(mcp): enable MCP_CONSENT_ENABLED on PROD approuter - #2698
Merged
Merged
Conversation
Add MCP_CONSENT_ENABLED="true" to the tutorials-prod-approuter properties in deploy/prod.mtaext so the Application Access Request consent screen is active on PROD after the next PROD MTA deploy. Verified end-to-end on DEV 2026-10-08 (consent page -> Allow -> IAS login -> token -> MCP transport connected). Chain: #2691 (authorize leg client_id) + #2693 (protected-resource discovery flip) + #2696 (DEV flag) + #2697 (token- exchange leg client_id). PRE-DEPLOY REQUIREMENTS (both must be done before this takes effect on PROD): 1. Seed MCP_CONSENT_STATE_SECRET in the PROD Credential Store (done). 2. Add https://<prod-approuter-host>/mcp-oauth/callback to the PROD IAS public client's OIDC redirect URIs (tutorials-identity app, shared tenant atxgsg7zi) — mirrors the DEV step. Without it IAS rejects the authorize leg. DEV branch per policy; reaches PROD via DEV->main release promotion.
jung-thomas
marked this pull request as ready for review
October 8, 2026 19:28
This was referenced Oct 8, 2026
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
1 participant
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
Adds
MCP_CONSENT_ENABLED="true"to thetutorials-prod-approuterproperties indeploy/prod.mtaext, so the Application Access Request consent screen activates on PROD at the next PROD MTA deploy.Verified on DEV
End-to-end on DEV 2026-10-08: consent page → Allow → IAS login → token → MCP transport connected (
StreamableHTTPClientTransport). Chain: #2691 + #2693 + #2696 + #2697.MCP_CONSENT_STATE_SECRETseeded in the PROD Credential Store — ✅ done.https://<prod-approuter-host>/mcp-oauth/callbackto the PROD IAS public client's OIDC redirect URIs (tutorials-identity, shared tenantatxgsg7zi) — mirrors the DEV step. Without it, IAS rejects the authorize leg. Not yet done — must happen before/with the deploy.Branch policy
Targets DEV per policy (no main-hotfix path); reaches PROD via DEV→main release promotion.
Note
PROD MCP client_id for the connect URL is
sb-tutorials-prod!t676072(vs DEV's0b1e8b56-…); users hit/mcp-auth/api(per-service mount — no bare/mcp/).