9.3.5. Relying Party Metadata¶

The openid_credential_verifier metadata MUST contain the client_metadata, as included in the parameters shown below. (Remote Credential Verifier Test Matrix). Please note that openid_credential_verifier is an OpenID Federation Wallet Architecture (OID-FED-WALLET) specific metadata used for OpenID4VP and it is used when the Relying Party's client_id is set with openid_federation. When the Relying Party's client_id parameter is set with x509_hash, the metadata is instead conveyed in the client_metadata parameter provided within the request.

Claim	Description
client_id	It MUST contain an HTTPS URL that uniquely identifies the RP. See RFC 7591#section-3.2.1 and Section 3.2 of [OpenID Connect Registration 1.0].
client_name	Human-readable string name of the RP. See RFC 7591#section-2.
logo_uri	URL of the entity's logo that will be shown to the User during interactions with the Wallet Instance. See OID-FED Section 5.2.2. The logo mime type MUST be `application/svg`.
application_type	String indicating the type of application. It MUST be set to "web" value. See Section 2 of [OpenID Connect Registration 1.0].
request_uris	JSON Array of request_uri values that are pre-registered by the RP. These URLs MUST use the https scheme. See Section 2 of [OpenID Connect Registration 1.0].
response_uris	JSON Array of response URI strings to which the Wallet Instance MUST send the Authorization Response using an HTTP POST request as defined by the Response Mode `direct_post` and `direct_post.jwt` (see OpenID4VP Sections 6.2 and 6.3).
redirect_uris	JSON Array of redirect URI strings for National `openid_federation` same-device endpoint binding. The Wallet Instance MUST validate a redirect URI against this value in the National path.
encrypted_response_enc_values_supported	JSON array of content encryption algorithms ("enc") the Verifier supports for encrypting the authorization response when using response mode `direct_post.jwt`. The Verifier MUST support both `A128GCM` and `A256GCM`. See ETSI TS 119 472-2 and OpenID4VP Sections 5.1 and 8.3.1.
vp_formats_supported	JSON object defining the formats and proof types of Verifiable Presentations and Verifiable Credentials the RP supports. It consists of a list of name/value pairs, where each name uniquely identifies a supported type. The RP MUST support at least `dc+sd-jwt`. For SD-JWT VC, the value associated with each name/value pair MUST include `sd-jwt_alg_values` listing acceptable signing algorithms; for mdoc-CBOR, the value MUST include `issuerauth_alg_values` and `deviceauth_alg_values`. The JOSE/COSE headers of presented artifacts MUST match one of the advertised values. See OpenID4VP §11 and Appendix B.
jwks	JSON Web Key Set document, passed by value, containing the request-specific ephemeral response-encryption public keys for the Relying Party. Every key MUST have `kid` and `use` values, and each `kid` MUST identify exactly one key. See JWK.

Note

The parameter response_uris is introduced in this specification. The Wallet Instance requests deletion of personal data through the Relying Party support contact, as specified in User's Attributes Deletion and in EUDI-TS 7.