feat(NK-WP-0032): admit OpenBao operator loopback callback
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02b90-83bf-75c2-81c8-aa705414e4d4
This commit is contained in:
tegwick 2026-08-23 13:58:18 +02:00
parent 6700f1c1c3
commit 61aeafef71
10 changed files with 150 additions and 10 deletions

View file

@ -95,8 +95,10 @@ See T03 retrospective for past realm drift bumps (now partially automated via ru
- Apply keycape-config Secret, restart KeyCape.
- Register bootstrap clients (netkingdom-bootstrap-console, openbao-admin).
- OpenBao admin redirects: localhost CLI callbacks plus
`https://bao.coulomb.social/ui/vault/auth/netkingdom/oidc/callback` for
preferred browser UI login; `keycape` remains a compatibility auth mount.
`http://127.0.0.1:18200/ui/vault/auth/netkingdom/oidc/callback` for the
preferred operator-tunneled browser UI login. The former public callback is
retained only for the bounded listener rollback window; `keycape` remains a
compatibility auth mount.
- Verify OIDC admin login: platform-root obtains OpenBao platform-admin via KeyCape/MFA.
- Evidence: keycape client gates, openbao_oidc_* , oidc_login_verified.
- Validate related in t02 / console.