Lutz Finsterle
21929fa899
Two isolated personal-credential backup options to evaluate, both excluded
from the admin policy (root-only break-glass):
- Scenario A: personal/ KV v2 (versioned) + personal-{put,get,list}.sh
- Scenario B: transit-personal/ key personal-backup + secret-{encrypt,decrypt}.sh
Plus an AppRole example of how a system should consume a secret:
- demo-app role/policy (read-only secret/demo-app/*), short-lived tokens
- scripts/app-get-secret.sh: login (role_id+secret_id) -> token -> read
All tokens/credentials live under ~/.config/openbao (outside the repo).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
9 lines
371 B
Bash
Executable File
9 lines
371 B
Bash
Executable File
#!/usr/bin/env bash
|
|
# Scenario A: list the names stored in the personal/ KV engine.
|
|
set -euo pipefail
|
|
ADDR="${BAO_ADDR:-http://127.0.0.1:8200}"
|
|
TOKF="$HOME/.config/openbao/personal-kv.token"
|
|
[ -r "$TOKF" ] || { echo "no token at $TOKF" >&2; exit 1; }
|
|
curl -sS -H "X-Vault-Token: $(cat "$TOKF")" "$ADDR/v1/personal/metadata?list=true" \
|
|
| jq -r '.data.keys[]? // empty'
|