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

docs: record verified identity provisioner credential repair
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a07ff8-19d0-7820-b4d0-1353833cb7fc
This commit is contained in:
tegwick 2026-09-11 22:00:37 +02:00
parent 2bc6e37f9f
commit c8ad7a85ea
4 changed files with 41 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/evidence/2026-09-11-native-portal-repair.md
View file

@ -60,3 +60,19 @@ seconds; Playwright opened temporary pages for previously visited origins.
After the operator reported the repeated page activity, the helper was stopped
and changed to cookie-only persistence. The confirmed tenant submission was not
repeated. This was helper-induced UI disruption, not evidence of a tenant failure.
A subsequent Create login failed before directory creation because the provisioner's
LLDAP admin login returned 401. Reloading the old credential did not repair it.
The operator then ran the reviewed identity-provisioner-reconcile.py apply with
the current provider password entered only at its hidden terminal prompt. The
sanitized receipt confirms provider_login=true, consumer_login=true and
provider_password_changed=false. Secret UID c6a9e6be-5bb5-47e6-9faa-06b8d72afec3
is unchanged; its resourceVersion advanced 51345775 to 60026132.
Independent verification after the operator receipt returned reloaded-check-passed
for directory authentication and a directory read from the provisioner. Deployment
is ready 1/1 and retains image
sha256:5b460f5ca9e329e287939f4707a2bb8d5674b7f94e24cfb5f6d790f54c3f8d06.
NK-WP-0036-T04 is complete. T05 retains structured dependency errors and functional
preflight; RAPPS-WP-0014 retains the actual native user login/password-setup proof.

22
docs/identity-provisioner-bind-repair.md
View file

@ -1,13 +1,13 @@
# Repair the identity provisioner's stored LLDAP credential
NK-WP-0036-T04, 2026-09-11. Prepared and tested; live apply has not run.
NK-WP-0036-T04, 2026-09-11. Attended live repair completed and independently verified.
The native User Engine Create login request reaches identity-provisioner, whose
LLDAP admin login returns HTTP 401 before identity creation. Reloading the
The native User Engine Create login request reached identity-provisioner, whose
LLDAP admin login returned HTTP 401 before identity creation. Reloading the
existing lldap-secrets reference did not fix it. The tenant and user-domain
records are independent and remain intact. Root portal login is working.
This is a proposed attended consumer-reference reconciliation. It does not
This procedure performs an attended consumer-reference reconciliation. It does not
rotate the LLDAP account, change signing keys, restore an exposed predecessor,
read a Secret payload, or rebuild KeyCape's configuration. The operator must
supply the currently working LLDAP `admin` password from existing custody through
@ -34,7 +34,9 @@ python3 sso-mfa/k8s/lldap/identity-provisioner-reconcile.py check
It authenticates the existing admin against the pinned in-cluster LLDAP URL and
performs a directory read. It changes no provider or consumer state.
After explicit operator acceptance, use the UID/resourceVersion from inspect:
Use the current UID/resourceVersion from inspect. The following command records
the accepted and completed 2026-09-11 execution; its old resourceVersion will
now be refused:
```sh
python3 sso-mfa/k8s/lldap/identity-provisioner-reconcile.py apply --expected-uid c6a9e6be-5bb5-47e6-9faa-06b8d72afec3 --expected-resource-version 51345775
@ -52,8 +54,14 @@ restored. Other login services and the LLDAP provider are not restarted.
Seven synthetic tests cover exact patch scope, stale metadata and controller
refusal, candidate rejection before writes, check-only behavior, stdin-only
value handling, redaction of child errors and the apply/reload/proof sequence.
The live metadata-only inspect succeeds. Live check/apply requires operator
input and is not claimed by those tests.
The operator subsequently supplied the working password only through the hidden
terminal prompt and completed apply. Its sanitized receipt reports result
reconciled, provider_login true, consumer_login true, and
provider_password_changed false. Secret UID is unchanged; resourceVersion is
now 60026132. Independent verification from the restarted consumer confirms
directory authentication plus a directory read. Deployment readiness is 1/1,
with its existing image digest 5b460f5ca9e329e287939f4707a2bb8d5674b7f94e24cfb5f6d790f54c3f8d06.
No native user/password-setup completion is inferred from these service checks.
After success, retry Create login only for the existing intended user, inspect
the returned password-setup page and record the native identity linkage.