#528 finish: custody status on the admin card, KV path escaping, provider dedup (v0.6.191) #537
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix-528d"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes out the remaining #528 scope:
encryptionPayloadnow emitscustodyStatus(errors, ttlSeconds, renewable, lastError) for OpenBao custody while the maintenance loop is active, sourced fromencrypt.CustodyStats()/CustodyLastError(). The custody pane renders a Custody token row (renews itself / cannot renew / does not expire, with a TTL badge) and a Last custody error row when one exists. i18n ×4. Numbers only — the no-secrets rule holds, the token itself never reaches the payload.url(rel)escaped nothing, so a#,%or?in a user or space name corrupted the request URL (%even made it unparseable). Each segment now goes throughurl.PathEscape.encrypt.New(store, buildKeys(cfg, log))— the near-duplicate switch was how the v0.6.189 maintenance wiring missed the in-process path. Bodies were verified token-identical before the collapse.TDD: red witnessed on the runner (URL corruption + missing custodyStatus), then green with the full suite and the #389 fence/node gates passing. CHANGELOG v0.6.191.