You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: openid-4-verifiable-presentations-1_0.md
+135-4Lines changed: 135 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1634,7 +1634,8 @@ The following is a non-normative example of a set of static configuration values
1634
1634
"kb-jwt_alg_values": [
1635
1635
"ES256"
1636
1636
]
1637
-
}
1637
+
},
1638
+
"mso_mdoc": {}
1638
1639
},
1639
1640
"request_object_signing_alg_values_supported": [
1640
1641
"ES256"
@@ -2733,7 +2734,137 @@ The VP Token contains the base64url-encoded `DeviceResponse` CBOR structure as d
2733
2734
2734
2735
### `Handover` and `SessionTranscript` Definitions
2735
2736
2736
-
#### Invocation via the Digital Credentials API
2737
+
#### Invocation via Redirects
2738
+
2739
+
If the presentation request is invoked using redirects, the `SessionTranscript` CBOR structure as defined in Section 9.1.5.1 in [@ISO.18013-5] MUST be used with the following changes:
2740
+
2741
+
*`DeviceEngagementBytes` MUST be `null`.
2742
+
*`EReaderKeyBytes` MUST be `null`.
2743
+
*`Handover` MUST be the `OpenID4VPHandover` CBOR structure as defined below.
2744
+
2745
+
```cddl
2746
+
OpenID4VPHandover = [
2747
+
"OpenID4VPHandover", ; A fixed identifier for this handover type
2748
+
OpenID4VPHandoverInfoHash ; A cryptographic hash of OpenID4VPHandoverInfo
2749
+
]
2750
+
2751
+
; Contains the sha-256 hash of OpenID4VPHandoverInfoBytes
2752
+
OpenID4VPHandoverInfoHash = bstr
2753
+
2754
+
; Contains the bytes of OpenID4VPHandoverInfo encoded as CBOR
The `OpenID4VPHandover` structure has the following elements:
2774
+
2775
+
* The first element MUST be the string `OpenID4VPHandover`. This serves as a unique identifier for the handover structure to prevent misinterpretation or confusion.
2776
+
* The second element MUST be a Byte String which contains the sha-256 hash of the bytes of `OpenID4VPHandoverInfo` when encoded as CBOR.
2777
+
* The `OpenID4VPHandoverInfo` has the following elements:
2778
+
* The first element MUST be the `client_id` request parameter. If applicable, this includes the Client Identifier Prefix.
2779
+
* The second element MUST be the value of the `nonce` request parameter.
2780
+
* If the response is encrypted, e.g., using `direct_post.jwt`, the third element MUST be the JWK SHA-256 Thumbprint as defined in [@!RFC7638], encoded as a Byte String, of the Verifier's public key used to encrypt the response. Otherwise, the third element MUST be `null`. See (#session_transcript_dc_api) for an explanation of why this is important.
2781
+
* The fourth element MUST be either the `redirect_uri` or `response_uri` request parameter, depending on which is present, as determined by the Response Mode.
2782
+
2783
+
Unless otherwise stated, the values of `client_id`, `nonce`, `redirect_uri`, and `response_uri` request parameters referenced above MUST be obtained from the Authorization Request query parameters if the request is unsigned, or from the signed Request Object if the request is signed.
2784
+
2785
+
The following is a non-normative example of the input JWK for calculating the JWK Thumbprint in the context of `OpenID4VPHandoverInfo`:
#### Invocation via the Digital Credentials API {#session_transcript_dc_api}
2737
2868
2738
2869
If the presentation request is invoked using the Digital Credentials API, the `SessionTranscript` CBOR structure as defined in Section 9.1.5.1 in [@ISO.18013-5] MUST be used with the following changes:
0 commit comments