coulomb/secrets-engine
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add named engine auth and accessor-file session revoke
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Select service-jwt, bootstrap, or env exclusively: JWT login uses a JSON
file, self-revokes, and never falls back to bootstrap or BAO_TOKEN. The
platform JWT mount/role is still unpublished, so auto keeps named
bootstrap/env providers.

session revoke --accessor-file revokes an already-issued token with
fingerprint-only evidence. Production remains fail-closed.

Assistant: grok
Assistant-Session: 01a05f07-ae72-7781-9fcb-19efd61add00
This commit is contained in:
tegwick 2026-09-02 01:24:08 +02:00
parent a94003de4f
commit 3abee434df
18 changed files with 698 additions and 135 deletions
Download patch file Download diff file Expand all files Collapse all files

18
SCOPE.md
View file

@ -152,9 +152,13 @@ do not replace exact-action authorization or OpenBao audit logs.
boundary.
- Never retries into or falls back to bootstrap, operator, or AppRole auth.
This provider is deliberately not connected to OpenBao. Signature verification
and token issuance remain with the platform-owned exact-bound OpenBao JWT role,
whose mount/role contract is still outstanding.
The CLI now has a named `service-jwt` provider that logs in through that
scaffold when the platform JWT mount/role contract is present, then
self-revokes the issued OpenBao token. Signature verification and token
issuance remain with the platform-owned exact-bound OpenBao JWT role, whose
mount/role contract is still outstanding. Until it is published, `--auth auto`
keeps named bootstrap/env providers and never treats them as a fallback from
service-jwt failure.
Treat their output as operational guidance, not complete attestation for
high-risk lanes.
@ -173,9 +177,11 @@ high-risk lanes.
catalog-id confirmation; it will remain closed until the canonical
exact-action approval contract in `SECRETS-WP-0007-T04` is enforced.
These operations do not manage external workload delivery. There is currently
no general lease/accessor operator command, rotation command, compromised state,
or persistent/reversible lane state machine.
These operations do not manage external workload delivery. `session revoke
--accessor-file` revokes an already-issued token by a non-secret accessor the
operator already holds; evidence is fingerprint-only. There is currently no
rotation command, compromised state, or persistent/reversible lane state
machine.
## CLI Surface