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
@@ -27,3 +27,6 @@ See `notes/P05-CI-01.md` and `tests/ci/`.
|
||||
|
||||
|
||||
**P05-OIDC-01:** New `p05-oidc-acceptance.yml` is **manual-only** with one disposable Docker job and `always()` owned cleanup. New `tests/ci/oidc_e2e/**` uses a short-lived ZITADEL IAM_OWNER PAT for official project/real client/test human provisioning, private portless browser network, original Login V2 Chromium username/password and real Auth.js callback/positive protected identity/negative access, with strict run-labeled browser/secret/Compose teardown. No Account/Login source, package, P02 developer Compose, real user or production change. **Actual Gitea runtime result pending**, no false PASS. See `docs/P05-OIDC-01.md` and `project/OIDC-E2E-ARCHITECTURE.md`.
|
||||
|
||||
|
||||
**P05-OIDC-01 final result:** [Gitea Run #90](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/90) on `cbcd60e` **FAILURE**. Manual-only P02 backend 4/4 healthy and host-portless PASS; run-labeled private localhost:8080 TCP forwarder readiness FAILED before any official OIDC client/human provisioning and before Chromium browser/auth callback. `always()` cleanup **PASS** (`ZITPLANE_BACKEND_CLEANUP_VERIFIED_PASS`, `ZITPLANE_OIDC_ALL_RESOURCES_CLEANED_PASS`). No repeat CI cycle. Next narrowly approved P05-OIDC-02 needed to determine whether sidecar exited, failed installing socat or could not bind/forward/rout; no authenticated OIDC E2E proof.
|
||||
@@ -13,7 +13,7 @@ Compact, developer-friendly monorepo for a central identity service, a branded l
|
||||
- **P05-SEC-01:** Gitea Run #87 **3 PASS / 1 FAIL**. Account and Login patched Next.js `16.4.6` builds PASS, Login 1219/1219 upstream unit tests PASS, Account audit 0. Login OpenTelemetry patched dependencies reduced prior 18 Moderate to **2 remaining** (glob/minimatch); strict Moderate security gate correctly FAILS. Current dependency patch retained; complete security acceptance requires a separate narrow transitive remediation phase. See `docs/P05-SEC-01.md`.
|
||||
- **P05-SEC-02:** Seven parent-scoped PNPM overrides resolved `glob`/`minimatch` advisories. Gitea Run #88 Login production audit **0 Moderate/High/Critical PASS**, but Login frozen install/build/units **NOT RUN** because a new CI override validator misparsed existing `>=` version ranges; post-run regex correction **not CI-verified**. Full acceptance **BLOCKED** pending a separately approved focused CI run. Account jobs intentionally skipped. See `docs/P05-SEC-02.md`.
|
||||
- **P05-SEC-02-A01:** **Gitea Run #89 SUCCESS** on `ff4c58e`: corrected exact override contract PASS, pinned PNPM frozen install PASS, official Login V2 standalone build PASS, upstream Vitest **1219/1219 PASS**, Login production audit **0 Moderate/High/Critical**; Account jobs skipped. **Dependency security/build unit acceptance complete; real user OIDC/MFA E2E and production integration NOT verified**. See `docs/P05-SEC-02-A01.md`.
|
||||
- **P05-OIDC-01:** Approved manual disposable real ZITADEL OIDC client/user + Chromium original Login V2/Auth.js callback/session/negative test harness, cleanup enforced; **actual CI pending**, no live production or auth source changes. See `docs/P05-OIDC-01.md`.
|
||||
- **P05-OIDC-01:** Gitea **Run #90 FAILED**: disposable four-service ZITADEL stack healthy and host-portless, but private `localhost:8080` loopback forwarding was not ready. Provisioning aborted before OIDC client/human/browser creation; real callback/session **NOT verified**. Owned database/bootstrap/secret/network cleanup **PASS**. No app/auth source change or deployment. See `docs/P05-OIDC-01.md`.
|
||||
- **Production / Coolify:** not configured or deployed.
|
||||
|
||||
## Documentation and project knowledge
|
||||
|
||||
@@ -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.
|
||||
+1
-1
@@ -15,6 +15,6 @@ This is the chronological **index**. Phase-specific scope/implementation evidenc
|
||||
| 2026-11-22 | P05-SEC-01 | Next.js 16.4.6, compatible OTel instrumentation, frozen locks and strict advisory gates | Run #87: 3 PASS/1 FAIL; 17/19 prior findings no longer reported, 2 Moderate Login blockers. [Evidence](P05-SEC-01.md) |
|
||||
| 2026-11-22 | P05-SEC-02 | Seven scoped parent overrides for glob/minimatch, pinned PNPM lock; one focused Gitea run | Run #88: Login security 0 findings PASS, build gate FAIL before frozen install on CI helper false-positive. Post-run regex fix unverified; [evidence](P05-SEC-02.md) |
|
||||
| 2026-11-22 | P05-SEC-02-A01 | One-run final acceptance of corrected CI parser and unchanged Login lockfile/seven overrides | **Run #89 SUCCESS** on `ff4c58e`: frozen install, standalone build and upstream 1219/1219 tests PASS; audit 0 Moderate/High/Critical; Account jobs skipped. [Evidence](P05-SEC-02-A01.md) |
|
||||
| 2026-11-22 | P05-OIDC-01 | Real disposable ZITADEL OIDC client/user, Chromium original Login V2/Auth.js callback/identity and owned-only cleanup | Source prepared; one focused Gitea run pending; [scope/evidence](P05-OIDC-01.md) |
|
||||
| 2026-11-22 | P05-OIDC-01 | CI-only official ZITADEL OIDC project/client/user and Chromium original Login V2/Auth.js acceptance harness with owned cleanup | **Run #90 FAILED**: 4 services healthy, no host ports; private localhost:8080 forwarder not ready, no user/client/browser created; cleanup VERIFIED PASS. [Evidence](P05-OIDC-01.md) |
|
||||
|
||||
Rules: Append new phases or fixes; never silently rewrite a past result. Separate **implemented**, **verified**, **blocked**, and **proposed**. Never log a user secret or personal data.
|
||||
+1
-1
@@ -11,7 +11,7 @@
|
||||
| [P05-SEC-01.md](P05-SEC-01.md) | Pre-change security scope, remediation, exact advisory evidence, one CI run and closure | P05-SEC-01 / Run #87 completed, 2 Moderate open |
|
||||
| [P05-SEC-02.md](P05-SEC-02.md) | Exact root chain, seven PNPM parent overrides, one focused Gitea CI and closure evidence | P05-SEC-02 / Run #88 security PASS, build blocked; parser post-run patch unverified |
|
||||
| [P05-SEC-02-A01.md](P05-SEC-02-A01.md) | Single-run Login-only final frozen/build/unit/security acceptance, scope lock and evidence | P05-SEC-02-A01 / Run #89 SUCCESS, accepted |
|
||||
| [P05-OIDC-01.md](P05-OIDC-01.md) | Pre-change real browser OIDC Scope Lock, provision/redirect/session/negative tests and one CI run evidence | P05-OIDC-01 / implementation prepared, real CI pending |
|
||||
| [P05-OIDC-01.md](P05-OIDC-01.md) | Pre-change real browser OIDC Scope Lock, provision/redirect/session/negative tests and one CI run evidence | P05-OIDC-01 / Run #90 FAILED at forwarder readiness; cleanup PASS; acceptance BLOCKED |
|
||||
| [CHANGELOG.md](CHANGELOG.md) | Short append-only chronological phase log and links to detailed reports | DOCS-01 / active |
|
||||
|
||||
Update this manifest whenever any direct child file or directory changes. Use **actual source state**; a planned file must be labeled planned, not present.
|
||||
+27
-1
@@ -2,7 +2,7 @@
|
||||
|
||||
**Date:** 2026-11-22
|
||||
**User-approved baseline:** `f423c696544f28a42d6a5d1ad0acfd88a3b6f56d` on Gitea `vibtools/ZitPlane/main`.
|
||||
**Pre-implementation state:** APPROVED / SCOPE LOCKED — this planning record is written before any CI implementation edits.
|
||||
**Phase status:** IMPLEMENTED IN SOURCE / ONE GITEA RUN #90 COMPLETED **FAILURE**. Real OIDC client/user/browser acceptance **BLOCKED** by private localhost:8080 forwarder readiness. Mandatory cleanup PASS. This plan was written before source edits.
|
||||
**Prior verified evidence:** Run #86 disposable backend/JWKS/DB persistence/teardown PASS; Run #87 Account build/security and negative authorization PASS; Run #89 Login V2 frozen standalone build/1219 tests and zero Moderate+ audit PASS. None proved a real authorization callback with a human user.
|
||||
|
||||
## Exact approved write scope and hard boundaries
|
||||
@@ -41,3 +41,29 @@ No local application installs/builds/tests/dev servers/Docker. No production dep
|
||||
- `GET /api/account/me` returns actual newly created user ID with private/no-store; protected Account page accessible with session, anonymous denied; malicious callback/session/issuer state rejected.
|
||||
- **Always-run** owned container/volume/network/credential cleanup verified.
|
||||
- No unauthorized repo changes, local builds/tests, fake PASS or production deployment. MFA/passkeys and production TLS **out of scope** unless actually verified with real flows; must remain deferred.
|
||||
|
||||
|
||||
## One focused Gitea CI cycle — actual terminal result, 2026-11-22
|
||||
|
||||
**Single authorized run:** [Gitea Run #90](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/90), job **#197**, tested **source SHA `cbcd60e76ec909df4f9c5826adf7a3e2a899c73e`**. `workflow_dispatch` on `main`. Created 2026-11-22 17:17:37 UTC; terminal 17:20:07 UTC. **Overall status completed, conclusion FAILURE.** No second CI run. Last commit after this run, if present, contains **only result documentation**, not a new verified source candidate.
|
||||
|
||||
| Job step | Result | Source-backed exact evidence |
|
||||
| --- | --- | --- |
|
||||
| Install Git before checkout and actions/checkout@v4 | **PASS** | Gitea job #197 steps #0/#1 both success |
|
||||
| Docker daemon + numeric run-owned preflight | **PASS** | `ZITPLANE_OIDC_DOCKER_PREFLIGHT_PASS` |
|
||||
| Portless Compose/CI IAM_OWNER configuration | **PASS** | `ZITPLANE_OIDC_NO_PUBLISHED_PORT_AND_OWNER_CONFIG_PASS`; no runner host port |
|
||||
| Disposable PostgreSQL, ZITADEL API, official Login V2 and Traefik health | **PASS** | Four containers healthy, `ZITPLANE_OIDC_FOUR_SERVICES_READY_PASS` |
|
||||
| CI-only private namespace localhost:8080 loopback forwarder readiness | **FAIL / BLOCKER** | `ZITPLANE_OIDC_PROVISION_BLOCKED: Disposable localhost issuer port forwarding was not ready` (~17:19:54 UTC) |
|
||||
| Real OIDC project/client/user API provisioning | **NOT EXECUTED** | `provision.py::wait_until_ready()` timed out first, before any API create request |
|
||||
| Real Chromium/Login V2/PKCE/state/nonce/authorization-code/Account session/negative browser checks | **NOT EXECUTED** | No project, client or human created; browser never started |
|
||||
| `always()` owned Docker cleanup job step #3 | **PASS** | `ZITPLANE_BACKEND_CLEANUP_VERIFIED_PASS`; `ZITPLANE_OIDC_ALL_RESOURCES_CLEANED_PASS` (~17:19:59 UTC); job cleanup step final success |
|
||||
|
||||
### Exact blocker, boundaries and remediation candidate
|
||||
|
||||
The CI code used a run-owned detached `alpine:3.21` sidecar sharing the proxy container network namespace and attempted `apk add --no-cache socat` (stdout/stderr suppressed) before starting a loopback listener from `127.0.0.1:8080` to proxy:80. The helper saw no working local endpoint within its bounded 70-second readiness poll. **The actual root cause is not yet proven**: the sidecar might have exited (e.g. package installation) or its listener/Traefik forwarding/Host routing could have failed. Because the sidecar's installation output was suppressed, **there is no diagnostic evidence proving which one**. This cannot be attributed to Auth.js, PKCE, user credentials or OIDC endpoints; none was exercised.
|
||||
|
||||
**Proposed P05-OIDC-02:** explicitly approve narrow CI-only `tests/ci/oidc_e2e/run.sh`, `provision.py` and, only if necessary, `cleanup.sh` changes to diagnose the run-owned sidecar's actual exit/running/listening state, prefer an immutable/pinned prebuilt socat image rather than first-installing a package after container start, verify local loopback readiness and exact issuer/Host routing before provisioning. Keep no host port, no leaked credentials or sensitive URLs, unchanged app/backend/Compose/PNPM source, and owned-only cleanup. Perform a **new separately approved single Gitea cycle** to test genuine provisioning and browser login; do not bypass authentication to satisfy it.
|
||||
|
||||
### Phase closure
|
||||
|
||||
**P05-OIDC-01 CI harness source IMPLEMENTED; interactive OIDC acceptance BLOCKED** on isolated network forwarding. **Safe CI-owned cleanup VERIFIED**, no resources left from run #90. All positive authenticated user/client/browser tests **UNVERIFIED**; MFA/passkey and production HTTPS/Console remain outside scope. Zero local app installs/builds/tests, no real identities/production deployment or source edits after Run #90. Unrelated untracked `AI_INSTRUCTIONS.md` untouched.
|
||||
@@ -15,7 +15,7 @@ This is the **developer-focused implementation history**. `notes/CHANGELOG.md` i
|
||||
| 2026-11-22 | P05-SEC-01 | Next.js/OTel minimal security manifests, reproducible locks, dedicated CI and strict Moderate+ gates | Run #87: Account/Login build PASS, Login Vitest 1219/1219, Account audit 0, Login 2 Moderate open; `notes/P05-SEC-01.md` |
|
||||
| 2026-11-22 | P05-SEC-02 | Seven parent-targeted glob/minimatch patched resolutions, PNPM lockfile metadata-only, manual Login-only CI and post-run validator fix | Run #88: strict Login audit 0 findings PASS, Login build job blocked before install by parser false-positive; post-run fix untested. `notes/P05-SEC-02.md` |
|
||||
| 2026-11-22 | P05-SEC-02-A01 | Verify existing corrected helper, exact seven PNPM scoped overrides, frozen Login Nx build and upstream Vitest; no source/lock changes | **Gitea Run #89 SUCCESS** on `ff4c58e`, 84/84 files, 1219/1219 tests, Login audit 0 Moderate/High/Critical; `notes/P05-SEC-02-A01.md` |
|
||||
| 2026-11-22 | P05-OIDC-01 | CI-only real OIDC IAM_OWNER bootstrap, project/client/user creation, Playwright password/callback/identity/negative tests and always cleanup | Source prepared; real CI outcome pending; `notes/P05-OIDC-01.md` |
|
||||
| 2026-11-22 | P05-OIDC-01 | Added manual disposable IAM_OWNER/client/human/browser OIDC acceptance harness, secret isolation and cleanup | Run #90 FAIL before provisioning: private loopback forwarder unready; 4 backend services healthy, owned cleanup PASS. `notes/P05-OIDC-01.md` |
|
||||
|
||||
## Required entry for each future change
|
||||
|
||||
|
||||
@@ -131,3 +131,6 @@ No new CI/auth/application/manifest/lock changes in A01; all checks were against
|
||||
New manual workflow `.gitea/workflows/p05-oidc-acceptance.yml` executes **one** isolated Docker runner job. `tests/ci/oidc_e2e/run.sh` creates the unchanged P02 stack under exact numeric run ownership and no host ports; a CI-only FirstInstance IAM_OWNER machine PAT and official API provision a disposable OIDC client/user. A pinned Chromium image runs the **unmodified** Account Portal in isolated CI development mode, driving official prebuilt Login V2 and real Auth.js PKCE/state/nonce, callback, authenticated Account API/page, negatives and local logout. An `always()` step calls `tests/ci/oidc_e2e/cleanup.sh` to remove only owned browser/forwarder/secrets and invokes audited backend owned-data cleanup. The run must fail if cleanup is incomplete; no browser secrets are logged/uploaded.
|
||||
|
||||
**Important:** The original backend external issuer is HTTP localhost, while Account Portal production mode correctly requires HTTPS. This **CI development-origin** browser acceptance does not certify production TLS, full self-hosted login source wiring, MFA or Admin Console human login. See `project/OIDC-E2E-ARCHITECTURE.md` for individual modules and `notes/P05-OIDC-01.md` for the actual run status.
|
||||
|
||||
|
||||
**P05-OIDC-01 real CI evidence:** Manual Gitea Run #90 (tested `cbcd60e`) had healthy 4-service portless backend PASS, **CI-only localhost:8080 namespace forwarder readiness FAIL**, no disposable OIDC project/client/user or Chromium browser launched; `always()` cleanup job step PASS, no leftover CI resources. Overall job FAILED; **not** an authenticated login test PASS. Next narrowly scoped P05-OIDC-02 must instrument/repair private forwarder lifecycle and reverify the full browser acceptance, without changing original application or backend code.
|
||||
@@ -127,3 +127,6 @@ Existing `tests/ci/security_advisory_gate.py` remains the independent **live reg
|
||||
- `tests/ci/oidc_e2e/browser.cjs::fixture()` checks fixture integrity; `waitForPortal()` checks the CI-only Account dev server; `assertAuthorization()` validates genuine browser authorization params (S256 PKCE, state, nonce, client and exact redirect); `verifyAnonymous()` asserts unauthenticated API 401/no-store and protected-page redirect; `verifyInvalidCallback()` asserts tampered state/code cannot establish a session; `main()` uses original Login V2 username/password, waits for a *real* Auth.js callback, verifies created user ID, cookie, protected page and local logout.
|
||||
- `run.sh` owns startup and preflight; `cleanup.sh` owns exact run-labeled teardown and failure if anything remains. These are not user-facing endpoints and must never run against shared/production Docker.
|
||||
- `users/ui/src/auth.ts`, Account/API source and all upstream Login V2 runtime functions remain unchanged.
|
||||
|
||||
|
||||
**P05-OIDC-01 runtime evidence:** `run.sh` reached four-service readiness in Run #90, then `provision.py::wait_until_ready()` timed out on private `localhost:8080` before `request()` could provision any client, project or user. Thus `browser.cjs::main()` and its positive/negative real login/session checks **were not executed**. The only other completed operation was `cleanup.sh`, which verified removal of owned state. The sidecar's precise root cause is unknown; avoid runtime/PASS claims for unexecuted browser functions.
|
||||
@@ -41,3 +41,12 @@ A first-instance IAM_OWNER service user is created only inside disposable ZITADE
|
||||
## References
|
||||
|
||||
ZITADEL official endpoints and bootstrap specification: `https://github.com/zitadel/zitadel/blob/main/cmd/setup/steps.yaml`, `https://zitadel.com/docs/reference/api/management/zitadel.management.v1.ManagementService.AddOIDCApp` and `https://zitadel.com/docs/guides/integrate/login-ui/username-password`. Actual Gitea result: `notes/P05-OIDC-01.md`.
|
||||
|
||||
|
||||
## Run #90 terminal evidence and network integration blocker
|
||||
|
||||
Gitea manual [Run #90](https://dev.ivib.cc/vibtools/ZitPlane/actions/runs/90), tested `cbcd60e76ec909df4f9c5826adf7a3e2a899c73e`, **FAILED**, job #197. `run.sh` correctly validated runner Docker/ownership, portless Compose with disposable first-instance IAM_OWNER configuration and brought all four P02 services up healthy. It created a private `alpine:3.21` namespace-sharing TCP forwarder; that helper attempted to install `socat` with its installation output silenced. The following `provision.py::wait_until_ready()` could not reach the expected private `localhost:8080` after 70 seconds and raised `ZITPLANE_OIDC_PROVISION_BLOCKED`. **The reason the forwarder was not ready remains unproven** (container exit, package install, socket bind or reverse-proxy routing cannot be distinguished from the available log). Do not misattribute failure to ZITADEL client provisioning or browser authentication: both were **NOT EXECUTED**.
|
||||
|
||||
The mandatory `cleanup.sh` step #3 succeeded and printed `ZITPLANE_BACKEND_CLEANUP_VERIFIED_PASS` + `ZITPLANE_OIDC_ALL_RESOURCES_CLEANED_PASS`. It removed only run #90-owned proxy namespace forwarder, separate ephemeral secrets volume, Compose containers, Postgres/bootstrap volumes and fixed CI network. **Backend bootstrap/cleanup PASS; full end-to-end OIDC acceptance BLOCKED.**
|
||||
|
||||
Next P05-OIDC-02 should narrowly instrument/check forwarder startup before provisioning, use an approved pinned prebuilt image to avoid silent runtime package installation, verify exact **private** loopback listener/Host routing without any host port exposure, preserve original Go backend/Compose/Login/Auth.js and credentials isolation, then run **one separately authorized** Gitea acceptance cycle. No CI-only patch in P05-OIDC-01 was executed after Run #90.
|
||||
@@ -1,6 +1,6 @@
|
||||
# ZitPlane ? exact tracked source inventory
|
||||
|
||||
**Snapshot:** 2026-11-22, P05-OIDC-01 source candidate on approved baseline `f423c69`. New browser OIDC integration is **NOT runtime-verified until actual Gitea CI**.
|
||||
**Snapshot:** 2026-11-22, P05-OIDC-01 source tested on Gitea Run #90 at `cbcd60e76ec909df4f9c5826adf7a3e2a899c73e`: backend/portless PASS, private localhost forwarder BLOCKED; no client/user/browser E2E executed, cleanup PASS. Final results-only documentation commit is NOT a new runtime test.
|
||||
|
||||
**Git-tracked file paths: 746.** Untracked `AI_INSTRUCTIONS.md` and ignored local secrets excluded.
|
||||
|
||||
|
||||
@@ -25,3 +25,6 @@ Add new CI checks and update `MINIFEST.md`, `project/`, `docs/`, and `notes/` in
|
||||
|
||||
|
||||
**P05-OIDC-01** is the new CI-only directory `tests/ci/oidc_e2e/`: exact files and first-party instructions in `README.md` and `MINIFEST.md` inside that folder. It is triggered **only** via new manual `.gitea/workflows/p05-oidc-acceptance.yml`. `run.sh` protects numeric run ownership, starts no-host-port official ZITADEL Compose, provisions a real disposable client/human via official IAM_OWNER PAT and runs pinned Chromium with the original Login V2 and unmodified Account Portal. It expects real PKCE/state/nonce/callback/session positive and negative results. `cleanup.sh` runs even on failure and must prove removal of **only** owned test containers, volumes, database/bootstrap credentials. **CI execution pending, not local tests or production proof.**
|
||||
|
||||
|
||||
**P05-OIDC-01 Run #90 terminal:** new `oidc_e2e/` harness started the original ZITADEL/PG/Login/Traefik services healthy with no host-published port. The private namespace loopback sidecar was **not ready**, so the provisioner timed out before creating a disposable project, OIDC client/user or running any browser checks. **No real OIDC accepted**. Gitea `always()` cleanup fully removed all run-owned volumes/containers/credentials and passed. No second run. P05-OIDC-02 should add safe CI-only startup/health diagnostics and pin the forwarder image before another single acceptance run.
|
||||
Reference in new issue
Block a user