I believe we're at the beginning of something extraordinary.
Today's AI agents are already impressive—they're helping software engineers write code, assisting site reliability teams in troubleshoo...
Your observations on the challenges and the necessary evolution of identity mechanisms, particularly OAuth, for AI agents, resonate deeply with our thinking in this space. I also share your perspective on the critical need for robust and adaptable identity solutions as AI agents become more prevalent and autonomous.
When initiating the authentication flow, the Agent(Actor) mentions that it (Actor) needs to act on behalf of the user
When requesting the token, the Agent(Agent) provides its own token (Actor token) to verify its identity
When issuing the token(JWT), the Auth Server validates the actor token to ensure it's valid, and the same as the party who initiated the flow in step #1, and includes the actor in the issued access token to indicate the delegation chain.
We believe it aligns closely with the direction you've outlined and offers a potential framework for addressing some of the challenges in the domain. We are doing R&D on solving the problems specific to IAM for AI. The shared IETF draft and follow-up sequence diagrams came out as part of those efforts.
Given our shared perspective and complementary work, we would be very interested in exploring potential avenues for collaboration and sharing further insights.
Thank you again for the thought-provoking article.
Thanks for sharing the flow diagram here. We've been working on some similar ideas, however I'm curious why you have the client in the flow here and what purpose it is serving? We have been thinking of the Agent/Actor being able to call API's on Resource Servers directly rather than needing to invoke a client to do that. Love to learn more about your thinking there.