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

Note loopback UI MFA succeeded; keep Ingress retraction gated.
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Operator confirmed 127.0.0.1:18200 login. The exact retract phrase is
still required before deleting the public OpenBao Ingress.

Assistant: grok
Assistant-Session: 01a0a23b-3bf0-7341-b4e5-9dc05f72573a
This commit is contained in:
codex 2026-09-15 02:33:12 +02:00
parent 66277450e3
commit 28424a615d
1 changed files with 7 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

7
workplans/RPF-WP-0025-openbao-operator-only-access.md
View file

@ -140,3 +140,10 @@ envelope. Public Ingress still present. CLI `bao login` used the contained
OIDC callback, not the UI loopback origin. T03 still needs one MFA login at OIDC callback, not the UI loopback origin. T03 still needs one MFA login at
`http://127.0.0.1:18200` before guarded retraction. Evidence: `http://127.0.0.1:18200` before guarded retraction. Evidence:
`docs/evidence/2026-09-15-openbao-loopback-callback-already-present.json`. `docs/evidence/2026-09-15-openbao-loopback-callback-already-present.json`.
Operator reported 2026-09-15 loopback UI MFA at `http://127.0.0.1:18200`
succeeded (boolean only; no token or screenshot). Named tunnel remains
lifecycle-healthy and public Ingress is still present. Guarded retraction is
the next hold: it requires the exact confirm phrase
`RETRACT RMASTER-WP-0020-T09 PUBLIC OPENBAO LISTENER`. Do not treat the UI
login "yes" as that phrase.