From f75b44186356ce452aa1ee92bb51a97e37b9aee2 Mon Sep 17 00:00:00 2001 From: Timo Glastra Date: Sat, 15 Mar 2025 14:45:02 +0100 Subject: [PATCH] add small note about client id parameters for dc api Signed-off-by: Timo Glastra --- openid-4-verifiable-presentations-1_0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openid-4-verifiable-presentations-1_0.md b/openid-4-verifiable-presentations-1_0.md index 9bf04373..621740b2 100644 --- a/openid-4-verifiable-presentations-1_0.md +++ b/openid-4-verifiable-presentations-1_0.md @@ -2181,7 +2181,7 @@ In addition to the above-mentioned parameters, a new parameter is introduced for * `expected_origins`: REQUIRED when signed requests defined in (#signed_request) are used with the Digital Credentials API (DC API). An array of strings, each string representing an Origin of the Verifier that is making the request. The Wallet can detect replay of the request from a malicious Verifier by comparing values in this parameter to the Origin. This parameter is not for use in unsigned requests and therefore a Wallet MUST ignore this parameter if it is present in an unsigned request. -Additional request parameters MAY be defined and used with OpenID4VP over the DC API. +Additional request parameters MAY be defined and used with OpenID4VP over the DC API, including parameters defined by a specific client identifier scheme (such as the `trust_chain` parameter for the `https` client id scheme). The Wallet MUST ignore any unrecognized parameters.