In part 1 I looked at the Credential Broker 4 Agents (CB4A) draft and argued that the agent should never hold a credential at all, and that a proxy (in our case agentgateway ) should exchange the user’s identity for the upstream token on the live request. That means the proxy’s token vault holds every user’s GitHub token, Slack token, etc. In part 2 I asked how much of the store an attacker can read when the process holding the token store is fully compromised .
Credential Injection Patterns for AI Agents: Part 3, Protecting the Token Vault with OpenBao
calendar_today
November 2, 2026
domain
agentgateway