Skip to main content

View Profile

In this walkthrough, John 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 last name and his password.

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 application renders the profile screen itself. Profile attributes are read from /users/me and ID token. Updates go through ThunderID's self-service endpoints: /users/me for attribute changes, /users/me/meta for schema metadata retrieve, 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 John.
  2. Open the account menu and select Profile. The sample reads John's attributes from his ID token and renders the View section.
  3. Edit the Last 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 John's profile page after a refresh. See User Types.

Going Deeper

  • Want to understand which attributes Wayfinder stores about John? See User Types in the Build It tutorial.
  • Prefer to define the Customer schema manually? See Model Your Users in the Build It tutorial.

Explore with AI

ThunderID LogoThunderID Logo

Product

DocsAPIsSDKs
© Copyright Linux Foundation Europe.For web site terms of use, trademark policy and other project policies please see https://linuxfoundation.eu/en/policies.