Comparing 2069b1332c..a7f2e2e6b3 - web - Gitea

groombook/web

Author	SHA1	Message	Date
Flea Flicker	a7f2e2e6b3	Merge pull request 'Promote dev → uat: GRO-2359 OOBE portal-creation routing' (#76 ) from promote/GRO-2359-dev-to-uat into uat CI / Test (push) Successful in 22s Details CI / Lint & Typecheck (push) Successful in 28s Details CI / Build & Push Docker Image (push) Successful in 14s Details Promote dev → uat: GRO-2359 OOBE portal-creation routing (#76)	2026-06-11 16:44:50 +00:00
Flea Flicker	a12bf019fa	feat(GRO-2359): route Authentik new-SSO users into OOBE (web) CI / Test (pull_request) Successful in 21s Details CI / Lint & Typecheck (pull_request) Successful in 29s Details CI / Build & Push Docker Image (pull_request) Successful in 15s Details The post-auth handler in CustomerPortal previously rendered the "Portal access not configured" card when the SSO bridge returned 404 (no client row for the user's email). That trapped first-time SSO users on a dead-end screen with no path to portal creation. This change routes the 404 to a new OOBE component (src/portal/OOBE.tsx) that drives portal creation: * Mounts inline inside CustomerPortal so the post-auth flow stays inside the portal render tree (no App-level router needed). * Also reachable as a direct deep-link via the new /onboarding route in App.tsx (for grooming admins or recovery flows). * Submits to a new POST /api/portal/clients-from-auth endpoint in groombook-api (companion commit) that creates a fresh client row bound to the Better Auth email. 409 means the email already has a portal record — the OOBE shows a portal-selection message. * Uses the canonical shared signOut() from lib/auth-client (GRO-2358 invariant) for the Sign out button. * Full window.location.href reload on submit success to reset the bridge's cached state and land the user in their portal. The no-access card itself is preserved for the deep-link deleted-portal case (a customer whose portal was disabled/deleted), signalled via ?noAccess=deleted-portal on a portal sub-route. The OOBE handles the first-time-creation case; the no-access card handles the "had a portal but lost it" case. Test coverage: * "routes to /onboarding when session-from-auth returns 404 (GRO-2359)" — proves the post-auth 404 mounts the OOBE inline, not the legacy no-access card. * 6 new OOBE tests: render from direct link, name prefill, form submission, 409 portal-selection, required-name validation, shared signOut(), redirect on no-session. * P1 no-access tests reworked to use ?noAccess=deleted-portal so the GRO-2358 signOut invariant is still verified on the only surviving path to the no-access card. UAT_PLAYBOOK §5.25.5–6e rewritten to cover the OOBE flow (form submit, 409, deep-link mount, deleted-portal no-access card). Paired with the api PR on feature/2357-p2-portal-clients-from-auth. Co-Authored-By: Paperclip <noreply@paperclip.ing> (cherry picked from commit `250c7a5ac9`)	2026-06-11 16:35:14 +00:00
Flea Flicker	bfe3ccf3b2	Promote dev → uat: GRO-2358 logout on no-access screen (#73 ) CI / Test (push) Successful in 19s Details CI / Lint & Typecheck (push) Successful in 24s Details CI / Build & Push Docker Image (push) Successful in 10s Details	2026-06-11 14:33:13 +00:00
Flea Flicker	b52b8e10ad	feat(GRO-2319): dev→uat — live StatusBadge palette (web) (#70 ) CI / Test (push) Successful in 21s Details CI / Lint & Typecheck (push) Successful in 27s Details CI / Build & Push Docker Image (push) Successful in 14s Details	2026-06-09 11:04:15 +00:00

Diff Content Not Available