Self Sign-Up
In this walkthrough, Emma 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.
Complete Set Up Your Environment before starting this walkthrough.
Enable Self Sign-Up 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
- Open http://localhost:5173. The Wayfinder home page loads.
- Select Sign in. The browser navigates to ThunderID.
- Select Sign up. The browser navigates to the ThunderID sign-up page.
- Fill in Emma's details — username
emma.wilson, emailemma.wilson@example.com, given nameEmma, family nameWilson, and a password — then submit. - ThunderID runs the sign-up flow: it creates a
Customeruser, records her terms acceptance, and assigns theTravelerrole. - The browser returns to Wayfinder. Emma 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.
Going Deeper
- Want to understand how user records and roles come together? See User Types, Roles, and Flows in the Identity Concepts.
- Prefer to build the registration flow manually? See Build the Registration Flow in Configure It Yourself.
