Configuration
Documentation Map
-
Configuration
-
Channel:
stable -
Source repo:
JaddaHelpifyr/jhf-keystore
Configuration
This page is the canonical configuration surface for jhf-keystore.
Runtime Modes
Supported provider modes:
cli- default and preferred
- reads via local
bwexecution
serve- loopback-only
- must stay local and explicitly guarded
jhf-keystore is not a remote secret service and must not expose a public write or read API.
Primary Environment Variables
Core runtime inputs:
VW_PROVIDERVW_BW_BINVW_BW_SERVE_URLVW_REQUIRE_LOCALBW_SESSIONVW_BW_SECRET_ENV_FILEBW_PASSWORD_ENV
Live-gated verification inputs:
VW_RUNTIME_DRIFT_VERIFY_LIVEVW_RUNTIME_DRIFT_VERIFY_HOSTVW_RUNTIME_DRIFT_VERIFY_USERVW_SSO_VERIFY_LIVEVW_PROJECTION_VERIFY_LIVEVOICE_V6_VERIFY_LIVEVOICE_W7_VERIFY_LIVE
Execution-policy rule:
- secrets or passwords may be injected at runtime
- secrets must never be checked into repo truth, docs, manifests, or evidence artifacts
Configuration Truth Sources
Canonical configuration surfaces:
- STACK_CONTRACT.md (
docs/STACK_CONTRACT.md) - ../contracts/runtime-stack-contract.json (
contracts/runtime-stack-contract.json) - ../contracts/vaultwarden-sso-consumer-runtime.json (
contracts/vaultwarden-sso-consumer-runtime.json) - ../contracts/non-interactive-bw-auth-bootstrap.md (
contracts/non-interactive-bw-auth-bootstrap.md)
Execution Hooks
Primary repo-owned verification hooks:
bash scripts/verify-docs-inventory-adoption.shbash scripts/verify-runtime-materialization-drift.shbash scripts/verify-vaultwarden-projection-presence.shbash scripts/verify-vaultwarden-sso-consumer-contract.sh
These hooks are the canonical readback path for configuration drift.
Known Limits
- no live secret values in docs or manifests
- no remote control plane
- no repo-owned reconciliation of upstream identity truth
AGPLv3. See LICENSE (LICENSE).
Learn more at helpifyr.com.