Policy demo
Auth brokering with HashiCorp Vault

Most teams store their secrets in a vault that agents don’t have access to, while agents tend to use any token they can find in the project. Qpoint’s auth broker replaces that token on the agent’s requests with a credential from HashiCorp Vault, so the token in the project is never sent. In the demo, GitHub receives the Vault credential instead of the personal token in the project’s .env file, and after the secret is rotated in Vault, the next request uses the new credential without a restart.
Gaurav Mahajan
Gaurav Mahajan
November 13, 2026

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.

See Qpoint in action in your environment
Request access and we'll get you set up.
Request Access