OpenBao is the open-source fork of HashiCorp Vault that powers Aurigraph's unified secret management plane across every product: V12, J4C, MEV Shield, Battua, Provenews, and the marketing website. One Vault, one auth model, per-project namespacing — no API keys in .env files, no secrets in container images.
.env
https://j4c.aurigraph.io/openbao
J4C Server (151.242.51.57) └── openbao container ├── /opt/openbao/data (file-backed storage) ├── /opt/openbao/audit.log (every access logged) └── KV v2 secret engine └── kv/aurigraph/ ├── v12/... (DLT-specific secrets) ├── j4c/... (J4C orchestration secrets) ├── mevshield/... (MEV Shield API keys) ├── battua/... (Battua signer roots) ├── provenews/... (Provenews C2PA keys) └── website/... (Mandrill, GA, OpenAI)
Every workload authenticates via AppRole (no passwords, no humans):
# Each container has its own RoleID + SecretID, mounted at entrypoint ROLE_ID=$(cat /run/secrets/openbao_role_id) SECRET_ID=$(cat /run/secrets/openbao_secret_id) VAULT_TOKEN=$(curl -s "$OPENBAO_HOST/v1/auth/approle/login" \ -d "{\"role_id\":\"$ROLE_ID\",\"secret_id\":\"$SECRET_ID\"}" \ | jq -r .auth.client_token) # Token TTL: 1 hour. Renewable 5 times. Hard cap: 8 hours.
Each project gets a dedicated KV namespace under kv/aurigraph/<project>/*. Access is enforced by least-privilege policies:
kv/aurigraph/<project>/*
v12-read
kv/aurigraph/v12/*
mevshield-read
kv/aurigraph/mevshield/*
battua-rotate
kv/aurigraph/battua/signer-roots
website-read
kv/aurigraph/website/*
A compromised website credential cannot read MEV Shield secrets. A compromised V12 credential cannot rotate Battua's signing root.
OpenBao uses Shamir-shared unseal keys (5 shares, threshold 3). After server reboot:
ssh -p 2244 subbu@151.242.51.57
docker exec openbao bao status
Sealed: true
docker exec -it openbao bao operator unseal <share-1> docker exec -it openbao bao operator unseal <share-2> docker exec -it openbao bao operator unseal <share-3>
bao status
Sealed: false
docker compose restart api website
Recovery shares are stored offline in three geographically separated locations. The runbook is part of the disaster-recovery playbook.
OpenBao tracks secret versions automatically. KV v2 keeps the last 10 versions. Rotation is a simple write:
bao kv put kv/aurigraph/battua/signer-root \ value=$(openssl rand -hex 32) \ rotated_at=$(date -u +%Y-%m-%dT%H:%M:%SZ)
Workloads pin to a specific version or follow ?version=current. Failed rotations roll back via bao kv rollback.
?version=current
bao kv rollback
Every read, write, and auth event is logged to /opt/openbao/audit.log in JSON format. The log is shipped to the J4C observability stack (Loki) for retention and SIEM ingestion. Audit log integrity is verified hourly against an HMAC chain.
/opt/openbao/audit.log
j4c.aurigraph.io/openbao
OPENBAO_CACERT=/etc/ssl/certs/ca-certificates.crt
Explore: About · Products · Features · Whitepapers · Sustainability · Tokenized carbon credits · Real-world asset tokenization · SDK · Blog · Plain-text site index · Sitemap · Contact: contact@aurigraph.io