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.

Prerequisites

Complete Set Up Your Environment before starting this walkthrough.

Background

Understand It covers the requirements story behind this use case.

Pick Your Pattern

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. Fill in Emma's details: username emma.wilson, email emma.wilson@example.com, given name Emma, family name Wilson, and a password. Then submit.
5. ThunderID runs the sign-up flow: it creates a Customer user and assigns the Traveler role.
6. 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 the architecture mapping in Understand It.

Going Deeper

• Want to understand how user records and roles come together? See User Types, Roles, and Flows in the Build It tutorial.
• Prefer to build the registration flow manually? See Build the Sign-In Flows in the Build It tutorial.