4.0 KiB
P05-OIDC-03 — Forwarder Startup Diagnosis & Real OIDC Acceptance
Approved baseline: 5f542a6aa376d06ba2c1fd3d46835baae9b8654e.
Prior evidence: Gitea Run #91 on 4831165548feabc2c0a0d39d25c40e0d1bc23bb2 — backend/Traefik private route PASS; socat exited 1; no client, user or browser created; owned cleanup PASS.
Current phase: Focused CI-only source candidate prepared; one real Gitea acceptance run required. No declaration of authenticated OIDC PASS without terminal evidence.
What changed
The manual .gitea/workflows/p05-oidc-acceptance.yml and original backend/Login/Account code are unchanged. Only tests/ci/oidc_e2e/run.sh adds bounded, secret-safe pre-provisioning diagnostics and a deterministic fallback:
- Reproduce the old
alpine/socat:1.8.1.3process once in the isolated proxy network namespace, with its verified repo sha256 digest. Check its actual running state andGET /debug/readywith exactHost: localhost:8080. - If socat exits or is unhealthy, classify only a known startup error class from the run-owned sidecar's stderr (such as bind/address/permission/argument) without printing any raw logs or HTTP body. The exact socat cause remains unknown until this CI evidence exists. Remove only its run-labeled container.
- Make at most one same-run switch to the official
python:3.12-alpineimage, validate its registry sha256 digest and runtests/ci/oidc_e2e/forwarder.pyin the same run-owned proxy namespace/container name. The Python standard-library code binds only IPv4 127.0.0.1:8080 and transparently relays opaque TCP bytes to 127.0.0.1:80; nopip, privileged port, host port or secret observation. - Fail closed before provisioning unless private forwarder
/debug/readyreturns HTTP 200 with original Host. The separately approvedprovision.py, Chromiumbrowser.cjs, Account Portal Auth.js and all negative authentication tests are unchanged. Existing mandatoryalways()cleanup still checks exact owner labels, Postgres, bootstrap PAT, credential volumes and no leftovers.
Exact acceptance
Full real-browser acceptance requires one actual successful Gitea CI run proving the private network, official disposable ZITADEL project/client/verified human provisioning, real original Login V2 password, code + PKCE S256/state/nonce and Auth.js callback, authenticated subject and protected Account pages/API, anonymous/invalid callback rejection, local logout and complete always() cleanup. A forwarder-only pass or a mere discovery/JWKS response cannot be called authenticated login.
No local application tests/builds/Docker, real users, production HTTPS, MFA/passkeys, tags or deployment. See notes/P05-OIDC-03.md for pre-change scope and exact actual run ledger; project/OIDC-E2E-ARCHITECTURE.md for source/network boundaries.
Real execution status — Gitea Run #93 queued, not yet accepted
A single approved Gitea Run #93 was dispatched on main using tested source SHA 7b80f411b2981e2274d171c12596301ed757b768. Its job #206 was still QUEUED at the last status inspection; no runner steps executed and no terminal conclusion exists.
Therefore socat startup classification, official Python digest fallback, private HTTP 200, ZITADEL project/client/human creation, real Chromium Login V2/PKCE/state/nonce/Auth.js callback, protected API/session, negative cases, and mandatory cleanup are all NOT EXECUTED / UNVERIFIED in Run #93. This is not evidence of a source regression or successful OIDC. No second CI run is permitted by this phase.
Next work is read-only runner scheduling/status inspection plus terminal evidence collection from the same Run #93 once it actually executes, then strict documentation-only closure. Original Login/Account/auth/Compose and dependencies remain unchanged; AI_INSTRUCTIONS.md was preserved. See notes/P05-OIDC-03.md for exact pre-edit Scope Lock and live snapshot.