Record provider credential renewal release and remaining owner handoff

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a092fe-13b1-7f12-ac74-7d258af4d79c
This commit is contained in:
tegwick 2026-09-13 14:27:35 +02:00
parent f4d8e44f0b
commit 78f5a718e9
2 changed files with 44 additions and 1 deletions

View file

@ -0,0 +1,40 @@
# Provider credential renewal release — 2026-09-13
Platform journey P05 consumer implementation, KEY-WP-0035-T04.
Source `632b1f1376cfcbde6340aed6137213ab79aa8708`.
Image `forgejo.coulomb.social/coulomb/key-cape@sha256:c9eb584d60efecfe00e1745a7e8cd3ebb4ae0f94faa715ef9594cd58a5dcebb6`.
Exclusive `adminTokenFile` supports per-request credential renewal for factor
lookup and OTP validation. Atomic file/symlink replacement is tested. Invalid or
missing input fails without stale/inline fallback or secret-bearing error text.
Regular absolute file input is bounded to 16 KiB. The default HTTP client refuses
redirects and bounds requests to ten seconds. OTP validation now requires both
provider success and a true validation result; false/missing success flags deny.
`go test ./...` passed, including five new test functions covering renewal,
invalid-source subcases, rejection/recovery, malformed provider outcomes and
redirect refusal. Authentication acceptance CI run 50 and image run 51 passed
for the exact source revision. The CI suite now executes on authentication source
changes. Synthetic test credentials only; no live factors or identities mutated.
Image-only live rollout used tests of cluster UID, deployment UID/resourceVersion
and predecessor image. KeyCape Ready 1/1. Four public provider checks passed:
health, readiness, OIDC discovery and the discovery-advertised JWKS endpoint.
Twelve isolated live Chromium recovery/sign-out checks passed. Pending issuer
login/code state is process-local and resets during Recreate replacement.
The source release includes previously tested optional-policy support, but no
client policy, credential value, mount or issuer signing-key configuration was
changed. Mounted-file renewal has NOT been activated live. The existing provider
credential failure is not claimed fixed. The owner must deliver and verify the
scoped credential, expiry/renewal and custody contract before enabling the file.
Canonical pin: net-kingdom/sso-mfa/k8s/keycape/deployment.yaml.
Rollback predecessor: `sha256:5f58563aa903ffa0c060e5ae9eb436aa963322d26bdde393efd2dd506dc6c4ed`.
Rollback was not required; it would restore the previous validation behavior.
Residual provider recovery/policy acceptance remains KEY-WP-0035-T02/T03 and
USER-WP-0030-T03. Owner contract
railiance-platform/docs/net-kingdom-credential-custody-contract.md remains draft
with required path/field placeholders; the registered route remains non-resolvable.
No live Secret read, issuance, renewal or policy mutation was performed.

View file

@ -63,10 +63,13 @@ KEY-WP-0034 and VERGABE-WP-0019; this work does not finish either workplan.
```task
id: KEY-WP-0035-T04
status: progress
status: done
priority: high
state_hub_task_id: "494f554d-6542-5797-804f-6df4a05dcadb"
```
Supports platform journey P05 and USER-WP-0030-T03. Add an exclusive mounted adminTokenFile credential source, fresh reads for lookup and validation, no stale fallback, bounded input, sanitized failures and atomic replacement acceptance. Preserve inline configuration compatibility. Require provider success and true validation value before AAL2; bound default request time and reject credential-bearing redirects. Test renewal, rejection, recovery and policy regressions. This implements the consumer delivery contract; owner credential issuance/custody and live P04/P05/P06 acceptance remain T02/T03.
All Go regression/conformance suites pass, including five new renewal/validation tests with invalid-source subcases. Added exact-commit authentication acceptance CI. Provider-mounted credential delivery and effective optional policy remain gated separately.
Consumer source 632b1f1 deployed and Ready 1/1; CI, four provider HTTP checks and twelve live browser checks passed. See docs/credential-renewal-release-2026-09-13.md. T02/T03 retain actual credential delivery and live recovery/policy acceptance.