One Login to Rule Them All: Cross-App Access for MCP
summary
Shows that a single SSO login issues access tokens across MCP servers using Identity Assertion Authorization Grant, with a live demo using Claude code and Okta to silently connect Figma via MCP. Eliminates repeated consent screens and converts dozens of manual OAuth flows into background token exchanges. Gives concrete requirements: XAA‑compatible SSO on clients, JWT‑bearer validation and token exchange on servers, short‑lived access tokens for immediate revocation and improved IT visibility.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:43MCP OAuth problems
- 6:34Cross-app access for MCP
- 9:43How XAA works
- 13:11Setup for IT and devs
- 16:39Security and future of XAA
- 17:00Q&A
related talks
26mSecure Your MCP Servers with OAuth, JWT, SPIFFE and More
27mSimple Control: Managing Multi-Domain MCP Access Via Keycloak IdP With ID-JAG
25mSecure Your MCP Servers With OAuth, JWT, SPIFFE and More
25mOAuth Gets You In, Zero Trust Keeps You Safe
25mModel Context Protocol(MCP) Authorization for Enterprise Use Case With Keycloak
29mKeeping Agents in Check: Apollo MCP Authentication
39mSecure Authorization for Agentic AI in Multi-Domain Environments
20mEvolution of MCP auth