Enterprise MCP rollouts hit the same wall: OAuth sprawl, shadow IT, and consent fatigue from per-server auth prompts. A new post from Yoshiyuki Tabata and Yutaka Obuchi at Hitachi walks through how ID-JAG support in Keycloak brings Enterprise-Managed Authorization (EMA) to the open source stack, so the IdP becomes the policy decision point for MCP server access. Open source EMA for MCP, no vendor lock-in. bit.ly/3UGQ3wx

Using Keycloak as an MCP authorization server. A new blog from Yasutaka Mitsumoto and @yo_tabata (AAIF Ambassador) explores why authorization is essential for MCP, how Keycloak maps to the MCP Authorization specification, and what teams should know when securing HTTP-based MCP servers with open source IAM. Read the blog: bit.ly/4w3Kjd0

Keycloak issues tokens as an OAuth 2.1 authorization server, so an MCP client can call an OpenAPI-based service through @agentgateway without touching the original application code. This walkthrough shows how to use agentgateway as an MCP gateway with Keycloak as the authorization server, exposing OpenAPI operations as MCP tools through the MCP authorization flow and OAuth 2.1, while keeping the existing API unchanged. Read the full blog post by AAIF Ambassadors @yo_tabata and Yasutaka Mitsumoto: aaif.io/blog/using-keycloak-… #MCP #OAuth #agentgateway

Existing OpenAPI APIs can become authorized MCP tools without changing the original application code. This walkthrough shows how to use @agentgateway as an MCP gateway with Keycloak as the authorization server to expose OpenAPI operations as MCP tools using the MCP authorization flow and OAuth 2.1, while keeping existing APIs unchanged. Read the full blog by @yo_tabata (AAIF Ambassador) and Michito Okai: aaif.io/blog/exposing-openap…