feat(GRO-2359): route Authentik new-SSO users into OOBE #75

2026-06-11T16:30:54Z

Flea Flicker commented

2026-06-11 16:30:54 +00:00

P2 — Route Authentik new-SSO users into OOBE (not the no-access screen)

## P2 — Route Authentik new-SSO users into OOBE (not the no-access screen)

Flea Flicker added 1 commit 2026-06-11 16:30:55 +00:00

feat(GRO-2359): route Authentik new-SSO users into OOBE (web)

CI / Test (pull_request) Successful in 25s

Details

CI / Lint & Typecheck (pull_request) Successful in 28s

Details

CI / Build & Push Docker Image (pull_request) Successful in 44s

Details

250c7a5ac9

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>

Flea Flicker merged commit 7a8b59ab87 into dev

2026-06-11 16:34:33 +00:00

Flea Flicker deleted branch feature/2357-p2-sso-to-oobe-routing

2026-06-11 16:34:33 +00:00

Flea Flicker referenced this pull request from groombook/api

2026-06-11 16:36:05 +00:00

Promote dev → uat: GRO-2359 clients-from-auth endpoint #213

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: groombook/web#75