oid4vp-metadata

Configure OID4VP authorization server, verifier, and client metadata parameters.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill oid4vp-metadata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oid4vp-metadata
Source: https://github.com/sourcelabbg/eudi-knowledge/tree/main/.ai/skills/oid4vp-metadata
Command: npx skills add https://github.com/sourcelabbg/eudi-knowledge --skill oid4vp-metadata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the complex process of configuring essential metadata for EUDI Wallet interactions, ensuring seamless communication and secure data exchange between wallets and verifiers.

Core Features & Use Cases

  • Metadata Configuration: Set up authorization server metadata, verifier metadata, and client metadata parameters.
  • Invocation Schemes: Define how wallets are invoked (e.g., openid4vp://, universal links, DC API).
  • Verifier Attestation: Implement secure verifier authentication using Verifier Attestation JWTs.
  • Use Case: A developer needs to ensure their verifier application can correctly communicate its supported credential formats and receive verifiable presentations from various wallets. This skill guides them through setting up the necessary vp_formats_supported and other parameters.

Quick Start

Configure the oid4vp-metadata skill to support jwt_vc_json format with ES256K and ES384 algorithms.

Frequently Asked Questions about oid4vp-metadata

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure wallet and verifier metadata for OpenID for Verifiable Presentations?

To configure wallet and verifier metadata for OpenID for Verifiable Presentations (OID4VP), you need to set up authorization server metadata, client metadata parameters, and Verifier Attestation JWTs to facilitate secure credential exchange.

What is the role of Verifier Attestation JWTs in OID4VP interactions?

Verifier Attestation JWTs provide secure verifier authentication during OID4VP interactions. They ensure the verifier is correctly identified and trusted before receiving verifiable presentations from wallets.

How do I define supported verifiable credential formats like jwt_vc_json in my verifier application?

You define supported verifiable credential formats by configuring the `vp_formats_supported` client metadata parameter, specifying formats like `jwt_vc_json` alongside accepted algorithms such as ES256K and ES384.

What invocation schemes can I use to trigger an EUDI Wallet for verifiable presentations?

Available invocation schemes to trigger an EUDI Wallet include custom URL schemes like `openid4vp://`, universal links, and the DC API, defining how wallets are launched for credential exchange.

When do I need to set up client metadata parameters for verifiable credential exchange?

You need to set up client metadata parameters when your verifier application must communicate its supported credential formats and authentication mechanisms to ensure interoperable data exchange with various wallets.

Does OID4VP metadata configuration support both ES256K and ES384 algorithms for JWT verifiable credentials?

Yes, OID4VP metadata configuration supports both ES256K and ES384 algorithms. You specify these within the `vp_formats_supported` parameter to define accepted cryptographic algorithms for JWT verifiable credentials.