Policy demoAuth brokering with HashiCorp Vault

About this demo
In this demo, Qpoint’s auth broker takes a credential from HashiCorp Vault and injects it into Claude Code requests to GitHub in place of the token that Claude used.
The Vault secret holds a read-only GitHub token created for agents. The project does not have access to it. The auth broker configuration specifies which secret to read and how often to check for a new version. The token that Qpoint uses to access Vault comes from a secret store, not from the configuration file.
Claude Code runs in a project with a .env file that contains a personal GitHub token. We ask Claude to list pull requests, which succeeds. In the audit log, we can see that GitHub received the token from Vault instead of the personal token from the .env file. Next, we rotate the secret using Vault’s API. We send the same prompt in the same session and observe in the audit log that the request used the refreshed token.