Enforce downscoping in token exchange for agent-to-agent calls
A Keycloak lab for A2A agents: the token B gets for C follows B's own scopes, not A's, unless you enforce downscoping. Stock run, control run and the fix.
Category
Lab notes. I set something up in a throwaway environment, write down what happened and what broke.
No posts in this audience.
A Keycloak lab for A2A agents: the token B gets for C follows B's own scopes, not A's, unless you enforce downscoping. Stock run, control run and the fix.
Lab: a GitHub workflow signs in to Azure with no secret. I print the sub of six kinds of run and show which credential lets each one in, pull requests too.
How ID-JAG and Cross App Access let a company's identity provider approve AI agent access to other apps, with lab screenshots and the draft's current status.
Lab in a test tenant: device-code sign-in, an agent API exchanging the token on-behalf-of with a certificate and no secret, and an unconsented scope failing.
A hands-on lab with Keycloak: an MCP server exchanges a user's token for a narrower one for a downstream API, then three bad exchanges are refused.
A lab with the official MCP Python SDK and Keycloak: the 401 handshake, audience checks, an RFC 8693 exchange for the payments API, and a refused passthrough.
Lab: a Container App agent with a user-assigned managed identity and no secrets gets one narrow app role, receives an app-only token, and the API validates it.