Skip to main content

Configure It Yourself

Use this page to build the Sky Pass setup manually instead of importing the declarative bundle. Pick this path when you want to see exactly what gets created, adapt the setup to your own project, or learn the moving parts step by step.

Prerequisites

Complete the environment steps in Set Up the Sample first — get ThunderID behind a public URL, point it at that URL, start it, and get the Wayfinder sample and the Skyline Lounge running. Then return here and follow the steps below instead of the bundle import.

The first section is the shared foundation — required regardless of which walkthrough you run. The remaining sections build on it.

Set Up the Foundation

The Sky Pass claims come from the credential subject's profile. The tryout needs a Customer user type with the loyalty attributes, and a test user (John Doe) whose values become the issued credential.

  1. Create the Customer user type.

    Navigate to User Types and create a new type. Set the name to Customer (category: User) and add the following attributes:

    AttributeTypeProperties
    usernamestringRequired, unique
    passwordstringRequired, credential
    emailstringRequired, unique
    given_namestringOptional
    family_namestringOptional
    full_namestringOptional
    member_idstringOptional
    tierstringOptional

    See User Types.

  2. Create John Doe.

    Navigate to Users and create a new user of type Customer. Set these values — they are what the walkthrough signs in as and what appears in the issued credential:

    AttributeValue
    usernamejohn.doe
    passwordjohn.doe
    emailjohn.doe@example.com
    given_nameJohn
    family_nameDoe
    full_nameJohn Doe
    member_idWF-100245
    tierGold

Set Up the Sky Pass Credential

The credential configuration defines what ThunderID issues over OpenID4VCI. In the Console, navigate to Verifiable CredentialsTemplates and create a new template:

  • Name: Wayfinder Sky Pass
  • Handle (identifier / scope): wayfinder-skypass — the create wizard auto-derives the handle from the name (as wayfinder-sky-pass); change it to wayfinder-skypass so it matches the sample's frontend and kiosk.
  • Type (vct): urn:wayfinder:skypass:1
  • Claims: full_name, given_name, family_name, email, member_id, tier — each sourced from the subject's profile and individually disclosable (SD-JWT).

The credential configuration's identifier doubles as the OAuth scope the wallet requests, so no extra scope registration is needed.

Set Up the Lounge Presentation

The presentation definition is what the Skyline Lounge asks the wallet to disclose. In the Console, navigate to Verifiable CredentialsPresentations and create a new definition:

  • Name: Skyline Lounge Access
  • Handle (identifier): wayfinder-skypass — as with the credential, override the auto-derived handle so it stays wayfinder-skypass (the kiosk requests this definition by that id).
  • Type (vct): urn:wayfinder:skypass:1
  • Mandatory claims: tier
  • Optional claims: full_name

Because only tier and full_name are requested, the wallet discloses just those two of the pass's six claims — the rest stay hidden.

Register the Wallet Clients

Each wallet vendor uses a fixed OAuth client_id and redirect URI for the OpenID4VCI flow, so register one application per wallet you want to support.

Using the Console (recommended)

In the Console, go to ApplicationsAdd Application and select Digital Wallet as the application type. On the Connect Your Wallet step, pick Heidi from the wallet dropdown — the Console pre-fills the client ID (c3ce7a6c-2bbb-4abe-909c-41bc9463d3c5) and redirect URI (ch.ubique.funke://issuance) automatically. Set Allowed User Types to Customer and finish the wizard. Repeat for Lissi (pre-fills 9c481dc3-2ad0-4fe0-881d-c32ad02fe0fc / https://oob.lissi.io/vci-cb).

With the foundation, credential, presentation, and wallet clients in place, continue to Issue Credential.

ThunderID LogoThunderID Logo

Product

DocsAPIsSDKs
© WSO2 LLC. All rights reserved.Privacy PolicyCookie Policy