Identity Templates

An Identity Template is a saved, reusable wallet configuration: trust framework, key type, OIDC settings, and the list of credential issuers and verifiers a wallet built from it will have. Creating a new wallet almost always starts with "pick a template, give it a name."

Finding Identity Templates

Go to Building Blocks in the top navigation. The page opens on the Identity Templates tab by default (the other tab is Credential Types, covered in Credential Types).

The list shows each template's Name (with a chip for its trust framework), Description, and a row of actions:

Icon	Action
🪪	Create identity from template — opens the "Create Wallet" dialog pre-filled with this template.
⬇	Export template — downloads the template as a JSON file.
✏	Edit template — opens the full editor.
🗑	Delete template — asks for confirmation ("This will permanently delete the template. This action cannot be undone.") before removing it.

Two buttons sit above the list: Import (see below) and New Template.

Creating a template

Click New Template. You'll first name it:

• Template Name (required)
• Description (optional, multi-line — use this to note what the template is for, e.g. "EBSI issuer for university diplomas")

Below that is the full wallet configuration form, described section by section next. When you're done, click Save Template, or Cancel to discard and return to Building Blocks.

Basic Settings

• Trust Framework (required) — EBSI, EUDI, IDTL, or NOOP. This choice is permanent for any wallet created from the template (it can't be changed on the wallet afterwards). See Introduction & Core Concepts if you're unsure which to pick — a tooltip next to the field also explains each option.
• Wallet Key Identifier (required) — how the wallet's key is identified: did (a DID, e.g. did:key, did:ebsi, or did:web), jwk, or x509 (a certificate — required before the wallet can be used). Like the trust framework, this cannot be changed after the wallet is created.

OIDC revision

Off by default, which uses safe defaults (Draft11 for OIDC4VCI, Draft16 for OIDC4VP — matching EBSI-compatible flows). Turn on "Configure OIDC revision" to choose explicitly:

• OIDC4VCI Draft — Draft11 or Draft15
• OIDC4VP Draft — Draft16 or Draft23

Use Draft15/Draft23 for anything that needs to interoperate with EUDI wallets; EBSI-facing flows expect Draft11/Draft16.

Framework Configuration

Shown only for EBSI, EUDI, and IDTL templates (not NOOP, which has no external registry). Click Configure (or Edit if already set) to open a framework-specific form:

• EBSI — conformance/pilot registry URLs (DID Registry, Trusted Issuers Registry, Trusted Schemas Registry, etc).
• EUDI — the ETSI Trusted List URL and its trusted root certificate(s), used to validate the EU trust chain.
• IDTL — framework-specific settings for the IDTL registry.

A Clear button removes the framework configuration if you need to start over.

Credential Issuers

This is where you turn the wallet into an issuer. Click Add Issuer to open the issuer definition form:

• Name (required) — a human-readable label for this issuer role, shown wherever the wallet offers this credential.

• Description (optional)

• Credential Type (required) — select from your account's Credential Types. This determines the data schema, format, and display of what gets issued.

• Signing Key Identifier — defaults to the wallet's own key type (did, jwk, or x509).

• Authorization — how a holder authorizes to receive this credential: none, oauthNoAuth, oauthCustom, openid, or openidCustom. The Custom variants require an Authentication Provider URL.

• Issuer Type (required) — controls the shape of the issuance flow:

  • IssuanceQueue — the simplest mode; credentials are queued and offered directly.
  • CredentialRequirements — the holder must first satisfy specific field values you define (a manual "authorization" checkpoint appears in the issuance wizard).
  • VPDriven — the holder must first present another credential (a Verifiable Presentation) before this one is issued.

  A tooltip on this field explains each option in place.

• Depending on the issuer type, additional fields appear: Credential Verifier ID (which verifier definition to check against), Credential Requirements (JSON), Mapping (JSON), and a "Use authentication provider result" checkbox.

• Disclosable Claims — a chip-input list of JSON paths that may be selectively disclosed at presentation time (relevant for SD-JWT VC credentials).

Existing issuers are listed with Edit and Remove actions. You can add as many issuer definitions as you need — typically one per credential type the wallet issues.

Credential Verifiers

This is where you turn the wallet into a verifier. Click Add Verifier to define what the wallet should request from a holder, using the same add/edit/remove list pattern as issuers. Each verifier definition describes what must be presented — either as a DIF Presentation Exchange definition or a DCQL query — and gets a Name used to label the "Verify" action in the wallet dashboard.

Import JSON

If you already have a raw wallet configuration (for example, exported from another environment, or one of Triveria's example templates), click Import JSON at the top of the form and paste it in. Nexus validates that it at least contains a trustFramework before applying it, then populates every field above from the pasted config.

Editing a template

Click the ✏ Edit icon on any row (or open it after creating). This is the same form pre-filled with the template's current values; save with Save Template.

Importing a template

Click Import above the list to open the Import Template dialog. Paste or upload a template JSON file exported from Nexus (or from another Triveria environment). On success you'll see a confirmation naming the template and any credential types it needed that were imported alongside it — templates carry their credential type dependencies with them so an issuer role never ends up pointing at a type you don't have.

Exporting a template

Click the ⬇ icon on any row to download that template as a JSON file — useful for backing it up, sharing it with a partner organization, or promoting it from a test environment to production.

Deleting a template

Click the 🗑 icon and confirm. This only deletes the template itself, not any wallets already created from it.

Creating a wallet from a template

Click the 🪪 icon on a template row (or see Managing Identities for the full wallet-creation flow) to open Create Wallet with this template pre-selected.

Continue to Credential Types.