coulomb/key-cape
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Correct the in-pod verify-client cause in the T04 receipt

Browse source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 132360@bnt-lap001
Assistant-Session: 769b1afd-4330-4c86-96b2-e510e26db42b
This commit is contained in:
tegwick 2026-10-07 13:57:05 +02:00
parent 6230e1706a
commit 4672ef5390
7 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/evidence/2026-10-07-secrets-engine-openbao-issuance.json
View file

@ -53,7 +53,7 @@
"human_login_after_restart": "founder OIDC login through KeyCape succeeded (the operator reader login above)",
"not_established": [
"the 900s token lifetime was not measured; it rests on the registration's tokenLifetime 15m",
"no in-pod verification: the deployed 1164f65 cannot fetch its own discovery document from inside the cluster (fixed in 8be8065)",
"no in-pod verification: verify-client inside the keycape pod failed at discovery of https://kc.coulomb.social. Corrected 2026-10-07: this is in-cluster reachability of the public issuer, not an image defect. 1164f65 already contains 8be8065, which concerns the upstream Authelia fetch, and main has no newer source",
"the OpenBao JWT role and login proof remain RPF-WP-0035-T02",
"the secrets-engine probe-openbao end-to-end run remains SECRETS-WP-0012-T03"
],