End-User Identity Propagation & On-Behalf-Of (OBO) Tool Execution #2312
djmcgreal-cc
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Key Use Cases:
Proposed Approach
Since kagent uses Google’s ADK under the hood for its execution engine, we could leverage ADK’s identity and token injection capabilities alongside kagent’s CRD architecture.
Context Propagation in Engine/CLI:
Extend kagent invoke and the UI backend to accept user authentication headers (e.g., OIDC Bearer tokens or K8s impersonation headers) and pass them as session context into the ADK runtime.
Declarative Auth in ToolServer CRD:
Introduce an optional auth spec field in the ToolServer custom resource:
ADK Tool Harness Injection:
When the ADK engine formats the MCP request to a ToolServer, the runtime checks the calling session's identity context and automatically injects the delegated user token into the tool invocation request headers.
This would make kagent the first K8s-native agent framework to offer zero-trust, enterprise-grade end-user identity delegation out of the box.
Would love to get maintainers' thoughts on whether this fits into the current roadmap or if there's an existing pattern being considered for user-scoped RBAC propagation!
All reactions