Give Agents the Right Keys - Identity Assertion for Enterprise APIs
summary
Enterprises gain a concrete fix for app‑to‑app and agent access: the Identity Assertion Authorization Grant (ID‑JAG) routes agent requests through the enterprise IdP so the IdP can authorize, log and enforce policy instead of apps exchanging long‑lived keys. The demo uses a todo app, agent0 and AWS Bedrock to show an ID token exchanged for a short‑lived IDJ token and then an access token, restoring visibility, governance and revocable credentials (references include RFC 8693 and the IETF draft).
AI-written summary · about
chapters (12)
- 0:00AI agent security challenges
- 1:34Enterprise identity management
- 2:37AI agents in enterprise workflows
- 4:02Unsecured agent risks
- 5:28Agent authorization approaches
- 7:32Problems with agent access
- 11:04Identity assertion for agents
- 12:10Cross-up access technicals
- 15:45Live demo: identity assertion
- 19:47Governance benefits
- 20:30Implementing identity assertion
- 21:18Q&A: machine-to-machine auth
related talks
25mIdentities and Authentication for Your Agents With Keycloak
25mSecuring Non-Human Identities: A Defense-in-Depth Blueprint for AI Agents
35mIdentity and Access Management for the Decade Ahead
19mHow to Secure Agents using OAuth
01h 22mIdentity for AI Agents
23mWho is Calling? Identity for Agents with AAuth
17mDon't give your agent the master key
19mDon't give your agent the master key