8.5 KiB
ZitPlane - Actual feature availability / limitations
Snapshot: 2026-11-22. Run #86 accepted isolated ZITADEL backend; Run #89 accepted frozen Login V2 production build, 1219 unit tests and strict zero-Moderate production dependency audit. Live authenticated OIDC, MFA and production still NOT verified. SOURCE EXISTS != RUNNING != VERIFIED != PRODUCTION.
| Feature | Source present | CI/build verified | Live/deployed |
|---|---|---|---|
| Official ZITADEL Go backend image configuration | Yes, P02 | Run #86 PASS: ZITADEL API healthy, local backend ready, OIDC discovery/JWKS | No |
| Local PostgreSQL and loopback Traefik stack | Yes, P02 | Run #86 PASS: Postgres restart persistence and portless CI Traefik healthy; developer PC stack not tested | No |
| Official prebuilt Login V2 service in local Compose | Yes, P02 configuration | Run #86 PASS: official Login V2 container healthy; interactive login flow not tested | No |
| Official Login V2 customisable source | Yes, P03 v4.20.4 | Run #89 PASS: frozen PNPM, Nx proto/client/Login Next 16.4.6 standalone build, 84/84 files and 1219/1219 unit tests; real login integration unverified | No |
| Login V2 signup/password/OTP/MFA/passkey/IDP source routes | Present upstream | Run #81 unit suite PASS; real account flows NOT tested | No |
| Custom Account Portal Next.js app | Yes, P04 | Run #83 npm ci/typecheck/Next production build PASS | No |
| Portal login OIDC and Auth.js callbacks | Yes, P04 source | No | No |
| Portal Overview / Profile / Security pages | Yes, P04 | No | No |
Read-only GET /api/account/me |
Yes, P04 | Run #83 anonymous 401/no-store and redirect negative cases PASS; positive auth unverified | No |
| Password/MFA/passkey changes inside Account Portal | No | N/A | No |
| Mutable profile editing / device sessions / identity deletion | No | N/A | No |
| Global ZITADEL SSO logout | No | N/A | No |
| Subscriptions, payments and SaaS billing | Outside ZitPlane scope | N/A | No |
| Gitea Actions CI verification workflow | Yes, P05 manual dispatch | Run #86 backend SUCCESS; Run #87 baseline, Run #88 partial, Run #89 Login build/security SUCCESS | Not deployed |
| Dependency Moderate security patch/acceptance | Next.js/OTel P05-SEC-01 patches, seven scoped glob/minimatch overrides and corrected CI validator | Run #89 PASS: Login audit 0 Moderate/High/Critical and frozen install/build/1219 unit tests; Account audit 0 in Run #87. This does not prove production auth/MFA | Not deployed |
| Gitea Actions CI and isolated integration tests | Backend-only workflow; interactive identity E2E remains absent | Run #86 PASS: disposable backend OIDC ready/discovery/JWKS, Postgres persistence, cleanup; authenticated user E2E pending | No |
| Coolify production stack, TLS, routing and backups | No | No | No |
Public auth.vib.tools/login URL |
Proposed only | No | No |
Public account.vib.tools account website |
Proposed only | No | No |
Prior historical P02 source-only Python static tests passed 3/3 in earlier work, and P03 upstream imported Git blobs matched 638/638. These are not equivalent to a running authentication system.
Future feature additions need an evidence-backed status update here, an exact developer implementation record in project/, a pre-change scope entry in notes/, and corresponding user guide updates.
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.
P05-OIDC-02 source prepared: CI-only prebuilt/digest-pinned socat, isolated proxy/Host and forwarded HTTP readiness gates, and strict status-only provisioner readiness have been added after the Run #90 blocker. Full browser/OIDC acceptance is still UNVERIFIED until one new terminal Gitea CI. Backend and previous Login build/unit/security PASS are not real authenticated session proof.
P05-OIDC-02 terminal status: Gitea Run #91 on 4831165 overall FAILURE: official backend four-service startup, no host ports and exact private Traefik routing PASS; pinned socat image/digest PASS, but forwarder process exited code 1, so all user/client provisioning and real Chromium Auth.js callback/session/negative tests NOT EXECUTED. always() cleanup PASS. Real authenticated OIDC remains BLOCKED; production TLS/MFA not evaluated.
P05-OIDC-03 planned CI acceptance: A same-run, safe error-class socat diagnosis and digest-verified Python stdlib private TCP fallback is prepared. The prior Run #91 verified private proxy route and cleanup but not any client/user/browser login. Full authenticated OIDC positive/negative flow remains UNVERIFIED until one actual Gitea run reaches and passes those contracts. MFA/passkeys and production TLS remain out of scope.
P05-OIDC-03 current CI evidence: Run #93 was dispatched on exact source 7b80f411b2981e2274d171c12596301ed757b768 but remains QUEUED at the last check; all actual OIDC/browser/fallback/cleanup checks NOT EXECUTED. The Python relay exists in source but its runtime compatibility is NOT VERIFIED. Run #91 remains last terminal evidence. No production login or MFA claimed.
P05-OIDC-03-A01 queue audit: Existing manual Run #93, job #206 was QUEUED (no start, steps or conclusion). Gitea job log returned 404 job not started; workflow active with ubuntu-latest label, but current runner availability cannot be confirmed. Every real OIDC project/client/user, browser callback/session, negative and mandatory cleanup gate NOT EXECUTED; Login security/build acceptance from earlier separate phases remains valid. See docs/P05-OIDC-03-A01.md.
P05-OIDC-03-A02 terminal update: Gitea Run #93 COMPLETED FAILURE (job #206 executed) after prior queued status. Four healthy services, portless networking, private Traefik Host route PASS. Socat SOCKET_BIND_ERROR and Python fallback ADDRESS_IN_USE on private 127.0.0.1:8080 BLOCKED further steps; actual listener not identified. Real client/user creation, Chromium Login V2, Auth.js callback/session, negative access and logout NOT EXECUTED. Mandatory owned-only cleanup PASS. Full authenticated OIDC and production/MFA remain UNVERIFIED.
P05-OIDC-04 terminal: Gitea Run #95, job #209, source 79dac4f5bb76e1cee4dfaf61657c6e84268b3dfb COMPLETED FAILURE. Docker/ownership/portless configuration PASS, four backend containers healthy PASS; direct private Traefik Host HTTP probe FAIL (OIDC_CI_PRIVATE_PROXY_SOCKET_OR_HTTP_BLOCKED). The 8080 PID/socket audit, new isolated forwarder and every real project/client/user/Chromium/Login V2/PKCE/Auth.js/session/negative/logout check were NOT EXECUTED. Owned-only cleanup PASS; authenticated OIDC remains BLOCKED, production/MFA NOT VERIFIED. See P05-OIDC-04.md.
P05-OIDC-04-A01 accepted real browser OIDC (disposable only): Gitea Run #96, job #210, source 670e225db477f180ff14ffa62e6654860a166f17 COMPLETED SUCCESS. 4/4 healthy services/portless network, actual Traefik PID 1 TCP6:8080 listener, separate private Socat forwarder, issuer discovery, official project/client/test-human, Chromium original Login V2, PKCE S256/state/nonce, genuine Auth.js callback/subject/session/protected identity API/page, anonymous/invalid-callback rejection, local logout and mandatory owned-only cleanup all PASS. Python fallback and transient-error retry NOT EXECUTED (not needed). Production HTTPS/custom imported Login V2 integration/MFA/passkeys/multi-app SSO/live deployment NOT VERIFIED. Full guide.