docs(ci): record P05 OIDC run 90 forwarder blocker and verified cleanup
This commit is contained in:
1 parent
cbcd60e76e
commit
b78270e9d4
17 files changed
+84
-8
No files matched your search
@@ -30,3 +30,6 @@ Future feature additions need an evidence-backed status update here, an exact de
|
||||
|
||||
|
||||
**P05-OIDC-01 source status (pre-run):** The new Gitea-only disposable IAM_OWNER → official OIDC project/client/human → real Chromium original Login V2/Auth.js positive callback/session/negative checks and strict cleanup harness is **IMPLEMENTED IN SOURCE**, **RUNTIME NOT YET VERIFIED**. Do not mark real login, production TLS, Admin Console or MFA as verified unless one actual CI run executes those exact assertions and succeeds.
|
||||
|
||||
|
||||
**P05-OIDC-01 terminal status:** Gitea Run #90 (`cbcd60e`) is **overall FAILURE**: disposable backend 4/4 healthy and portless PASS, but private localhost:8080 forwarder unready, blocking all OIDC project/client/human and real browser callback/session/negative tests. **Nothing authenticated was verified.** `always()` cleanup succeeded and verified no owned containers/volumes/network/credentials remained. Future P05-OIDC-02 needed; production/MFA remains untested.
|
||||
+1
-1
@@ -13,7 +13,7 @@ Every file listed below is a direct child of `docs/`. Add/remove rows whenever t
|
||||
| [P05-SEC-01.md](P05-SEC-01.md) | Source-grounded dependency security patches, advisory blockers and CI verification | P05-SEC-01 / Run #87 3 PASS/1 FAIL, 2 Moderate open |
|
||||
| [P05-SEC-02.md](P05-SEC-02.md) | Seven scoped PNPM parent overrides, patched lock and manual Login-only security CI evidence | P05-SEC-02 / Run #88 partial: security zero, build unverified |
|
||||
| [P05-SEC-02-A01.md](P05-SEC-02-A01.md) | Gitea-only Login V2 full frozen-install/build/units/zero-advisory acceptance and status | P05-SEC-02-A01 / Run #89 SUCCESS |
|
||||
| [P05-OIDC-01.md](P05-OIDC-01.md) | How isolated real OIDC Login V2 browser/session checks work; real CI status/limitations | P05-OIDC-01 / run pending |
|
||||
| [P05-OIDC-01.md](P05-OIDC-01.md) | How isolated real OIDC Login V2 browser/session checks work; real CI status/limitations | P05-OIDC-01 / Run #90 BLOCKED before provisioning; cleanup PASS |
|
||||
| [SETUP-GUIDE.md](SETUP-GUIDE.md) | Operator/developer prerequisites, configs, activation and safety | DOCS-01 / active; runtime pending |
|
||||
| [FEATURES-STATUS.md](FEATURES-STATUS.md) | Exact implemented/unavailable/unverified feature matrix | DOCS-01 / active |
|
||||
| [TROUBLESHOOTING.md](TROUBLESHOOTING.md) | Known blockers and safe diagnosis based on source status | DOCS-01 / active |
|
||||
|
||||
+10
-1
@@ -2,7 +2,7 @@
|
||||
|
||||
**Approved baseline:** `f423c696544f28a42d6a5d1ad0acfd88a3b6f56d`
|
||||
**Planned verification:** manual Gitea Actions `.gitea/workflows/p05-oidc-acceptance.yml`
|
||||
**Status:** CI-only implementation prepared; **NO real browser login or cleanup accepted until the focused Gitea run completes**.
|
||||
**Status:** **Gitea Run #90 FAILED**: four services healthy, no host ports; localhost:8080 forwarder not ready and provisioning aborted *before* disposable OIDC client/user/browser creation. **Mandatory owned-only cleanup PASS**. Real interactive OIDC remains BLOCKED.
|
||||
|
||||
## What this phase actually tests
|
||||
|
||||
@@ -24,3 +24,12 @@ The user test credentials, admin PAT, OAuth codes, cookies and browser URLs with
|
||||
Authorize and dispatch the **one** manual workflow under Gitea [ZitPlane Actions](https://dev.ivib.cc/vibtools/ZitPlane/actions). Do not trigger it outside a dedicated Docker runner. A full PASS needs **all** official client/user creation, real browser password/callback/positive and negative identity evidence and complete owned resource teardown, verified by named CI markers and final job SUCCESS. If the runner lacks Docker, a provisioning API is incompatible, real authorization cannot complete, or cleanup fails, the phase remains **BLOCKED** with the exact verified point of failure; it is not silently downgraded into metadata/JWKS smoke.
|
||||
|
||||
**Not covered:** human MFA/passkeys, Admin Console human E2E, production HTTPS/TLS issuer, source-built Login V2 runtime wiring, real global SSO logout and production Coolify deployment. These are separate explicit Scope Locks. The final actual Gitea results are recorded in `notes/P05-OIDC-01.md`.
|
||||
|
||||
|
||||
## Actual Gitea Run #90 — BLOCKED, resources cleaned
|
||||
|
||||
[Run #90](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/90) tested `cbcd60e76ec909df4f9c5826adf7a3e2a899c73e`. Job #197 **FAILED** after the approved disposable PostgreSQL/ZITADEL API/official Login V2/Traefik stack became healthy and the no-published-host-port configuration passed. The CI-only localhost:8080 forwarder did **not** become ready; the provisioning helper emitted `ZITPLANE_OIDC_PROVISION_BLOCKED: Disposable localhost issuer port forwarding was not ready`. **No OIDC project, client, human test account, Chromium sign-in or Auth.js callback was created/tested**. Do not describe OIDC as working or accepted.
|
||||
|
||||
**Safety verified:** `always()` step #3 succeeded: `ZITPLANE_BACKEND_CLEANUP_VERIFIED_PASS` and `ZITPLANE_OIDC_ALL_RESOURCES_CLEANED_PASS`, removing only owned database/bootstrap/containers/credentials/volumes/network. No production deployment, real accounts or host ports used.
|
||||
|
||||
**Next:** The precise reason the forwarder failed is **not yet known** because package installation/logs were suppressed. A separately approved P05-OIDC-02 should instrument the *CI-only* sidecar's safe health/exit diagnostics and use a pinned prebuilt forwarding image, then repeat **one** isolated Gitea browser/provisioning acceptance. No Login/Auth.js source edit, IAM bypass, production HTTP or claims of verified browser authentication. Full job IDs, evidence and Scope Lock: `notes/P05-OIDC-01.md`.
|
||||
@@ -84,3 +84,12 @@ Compact login and account UI, accessibility, responsive design and scoped regres
|
||||
|
||||
## P07 - Production deployment (proposed, NOT approved)
|
||||
Coolify, HTTPS, secrets, backups, durable storage and focused production readiness; explicit approval required.
|
||||
|
||||
|
||||
## P05-OIDC-01 actual acceptance result — 2026-11-22
|
||||
|
||||
- Approved baseline `f423c696544f28a42d6a5d1ad0acfd88a3b6f56d`; tested source commit `cbcd60e76ec909df4f9c5826adf7a3e2a899c73e`.
|
||||
- **One** Gitea Actions Run #90, job #197, **overall FAILURE**. Repo checkout/Docker preflight PASS, no published host ports PASS, official four-container disposable backend startup/health PASS.
|
||||
- **Blocker:** private run-owned localhost:8080 forwarder did not become ready in bounded 70 seconds; no admin API project/client/human provisioning or Chromium PKCE/state/nonce/callback/session/negative tests were executed. Exact sidecar cause **unknown** with current suppressed diagnostics. **Interactive OIDC acceptance BLOCKED**.
|
||||
- **Safety PASS:** mandatory `always()` cleanup step succeeded: `ZITPLANE_BACKEND_CLEANUP_VERIFIED_PASS`, `ZITPLANE_OIDC_ALL_RESOURCES_CLEANED_PASS`. No production users/secrets/ports/deployment affected.
|
||||
- No local application tests/builds, no second Gitea run, no original backend/Login/Auth.js source/manifest edits. Next P05-OIDC-02 requires separate exact scope approval limited to CI-only forwarder readiness/observability, then one new isolated full OIDC run. Full evidence `notes/P05-OIDC-01.md`, operator guidance `docs/P05-OIDC-01.md`.
|
||||
@@ -105,3 +105,6 @@ Use Gitea Actions → **ZitPlane P05 Dependency Security Acceptance (SEC-01/02)*
|
||||
## P05-OIDC-01 — isolated real-user OIDC verification, Gitea only
|
||||
|
||||
In Gitea `vibtools/ZitPlane` → Actions → **ZitPlane P05-OIDC-01 Disposable Real Browser Acceptance** → manual Run workflow on `main` only when explicitly approved. The workflow provisions its own short-lived IAM_OWNER PAT, isolated ZITADEL project/client/verified test human, then tests the actual ZITADEL Login V2 username/password and Auth.js Account callback in Chromium. It does **not** use your real users, public domain, production secrets or host-published HTTP ports. It removes its test credentials, browser and isolated database/volumes via an `always()` step; any cleanup failure prevents phase acceptance. See `docs/P05-OIDC-01.md` for the expected checks and current real run result. This test uses CI-only HTTP loopback (Account development mode), **not** the actual production HTTPS issuer.
|
||||
|
||||
|
||||
**P05-OIDC-01 actual Gitea evidence:** [Run #90](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/90) started the original ZITADEL/PostgreSQL/Login V2/Traefik stack healthy without publishing host ports, but could not establish private `localhost:8080` forwarding. Official OIDC project/client/user setup and real browser callback **did not execute**; overall CI FAILED. Mandatory owned-only resource cleanup **PASSED**. The run did not impact production or user accounts. A separately scoped P05-OIDC-02 CI network-forwarder acceptance is needed before claiming interactive OIDC works.
|
||||
@@ -55,3 +55,8 @@ The earlier Run #88 CI helper misread `axios@>=` and similar version-range keys
|
||||
## P05-OIDC-01 — isolated real OIDC browser acceptance troubleshooting
|
||||
|
||||
The new manual Gitea `p05-oidc-acceptance.yml` is **not a production deployment**. If runner Docker ownership preflight fails, do not delete an existing network/volume or reuse secrets; use a clean runner. If IAM_OWNER PAT or API client/user creation fails, do not use P02's restricted `IAM_LOGIN_CLIENT` PAT as a substitute. If the original Login V2 browser or Auth.js callback fails, report only the safe blocker marker and do **not** mock tokens, disable PKCE/state/nonce or alter production auth source. If cleanup cannot prove empty run-owned Docker resources, the job must remain FAILED. The HTTP localhost issuer works only in the private Gitea CI development environment; production HTTPS requires a separate Scope Lock. Exact current evidence: `notes/P05-OIDC-01.md`.
|
||||
|
||||
|
||||
## P05-OIDC-01 Run #90 — private loopback forwarder NOT ready
|
||||
|
||||
Job #197 in [Run #90](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/90) failed after four healthy backend services. The CI-only forwarding sidecar never made `localhost:8080` reachable within the 70-second provisioner wait. The sidecar suppresses its `apk add socat` startup diagnostics, so its **exact failure cause is not confirmed**. **Do not** disable issuer checks, expose port 8080, reuse an IAM_LOGIN_CLIENT token as admin or modify protected Auth.js/Login V2 source. The proper next step is a separately approved narrow CI-only forwarder diagnostics/pinning fix, followed by one isolated run. `always()` cleanup **PASS**; no CI-owned Docker resources remained. No real client/user/browser OIDC assertions ran.
|
||||
Reference in new issue
Block a user