Profile Section

In this walkthrough, Thor opens his Wayfinder profile and exercises the two parts of the use case. He views what Wayfinder stores about him: name, email, and the other attributes on his Customer record. He then updates the values he wants to change: his display name and his password.

Prerequisites

Complete Setup before starting this walkthrough.

Background

Add a Profile Section covers the requirements story behind this use case.

Pick Your Pattern

Redirect-based

In the redirect-based pattern, the consumer app renders the profile screen itself. Profile attributes are read directly from ID token, and updates go through ThunderID's self-service endpoints — /users/me for attribute changes and /users/me/update-credentials for password changes. These endpoints act on the signed-in user's own record, so no extra permissions are needed; the access token alone is enough.

Try the Use Case

1. Open http://localhost:5173 and sign in as Thor.
2. Open the account menu and select Profile. The sample reads Thor's attributes from his ID token and renders the View section.
3. Edit the Display Name field and select Save.
4. Select Change Password, enter the current password, set a new one, and save.

Try a Variant

• Add a new attribute to the Customer schema (for example, seatPreference) and verify it appears on Thor's profile page after a refresh. See User Types.

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.