Self Sign-Up

In this walkthrough, Sif signs up for Wayfinder with her email and a password, and arrives at the dashboard ready to make her first booking. ThunderID creates a Customer user record from her input and attaches the Traveler role so she has booking permissions from her first session.

Prerequisites

Complete Setup before starting this walkthrough.

Background

Enable Self Sign-Up and Registration covers the requirements story behind this use case.

Pick Your Pattern

Redirect-based

In the redirect-based pattern, the consumer app sends the user to ThunderID for the entire sign-up experience and returns them as a signed-in user with tokens attached. The Wayfinder web frontend is configured exactly this way. The Sign in button triggers an OIDC redirect to ThunderID, where a new user picks Sign up, completes the form, and is returned to Wayfinder with an access token.

Try the Use Case

1. Open http://localhost:5173. The Wayfinder home page loads.
2. Select "Sign in". The browser navigates to ThunderID.
3. Select "Sign up". The browser navigates to the ThunderID sign-up page.
4. Enter Sif's email, a password, and any required profile attributes. Submit.
5. ThunderID runs the sign-up flow: it creates a Customer user, records her terms acceptance, and assigns the Traveler role.
6. The browser returns to Wayfinder. Sif arrives at the dashboard, ready to make her first booking.

Try a Variant

• Add Google as a federated sign-up option. See Federation under Cross-Cutting Capabilities.

App-native step-by-step

Coming soon. See the App-native pattern for what to expect.

App-native managed

Coming soon. See the App-native pattern for what to expect.

Direct API

Coming soon. See the Direct API pattern for what to expect.