HashiCorp Vault¶
Vault uses broker-owned vault CLI authentication and environment tokens.
Broker Setup¶
Install the Vault CLI in the broker/container image:
./scripts/build_docker_image.sh --credential-clis vault team-assistant:vault
Broker-only env:
VAULT_ADDR=https://vault.example.com
VAULT_TOKEN_FILE=/run/secrets/vault_token
VAULT_KV_MOUNT=secret
VAULT_KV_MOUNT selects the default KV mount and defaults to secret.
Vault can also back broker credential-state storage for GitHub token auth and
Google gog token/client JSON imports:
security_layer:
credential_state_backend:
mode: credential_source
source: vault
namespace: agent-credential-store
fallback_to_files: false
Stored broker payloads are written under that namespace.
Chat Command¶
/auth vault
This reports broker-side status and setup guidance. It does not open a web form.
Supported Broker Actions¶
credential.searchcredential.get_metadatacredential.use_for_action
Verification¶
- Confirm
vaultis installed in the broker container. - Confirm
VAULT_ADDRpoints to the correct Vault. - Confirm
VAULT_TOKENorVAULT_TOKEN_FILEis broker-only. - Run
/auth vault. - Search metadata under the intended KV mount/folder.
- Confirm secret values are not printed.