feat(mcp): Enterprise-Managed Auth (id-jag) validation + Okta docs#2798
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
…drop wrong client JSON
… redirect old azure-apim path
enesgules
approved these changes
Jun 22, 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
2 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.
Adds MCP-server validation for Enterprise-Managed Auth (id-jag) access tokens and admin docs for the Okta flow.
validateJWTaccepts Context7-issued EMA access tokens via a new issuer branch, verified against the authorization server's public JWKS with an audience check.EMA_ISSUER/EMA_JWKS_URLconstants.enterprise/enterprise-managed-auth/oktawalkthrough (Okta Cross-App Access setup, Context7 config, troubleshooting) under a new Enterprise-Managed Auth nav group.