From 0b7c0d4221b5b0cf5581c38cbdb089d27ae70ad0 Mon Sep 17 00:00:00 2001 From: Michael Jones Date: Sun, 18 Aug 2024 17:23:19 -0700 Subject: [PATCH] Detached payloads may be used --- index.html | 26 ++++++++++++++++---------- 1 file changed, 16 insertions(+), 10 deletions(-) diff --git a/index.html b/index.html index 4161085..dc4902f 100644 --- a/index.html +++ b/index.html @@ -250,7 +250,8 @@

Securing JSON-LD Verifiable Credentials with JOSE

A [=conforming JWS issuer implementation=] MUST use [[RFC7515]] to secure this media type. - The unsecured verifiable credential is the unencoded JWS payload. + The unsecured [=verifiable credential=] is the unencoded JWS payload. + A detached payload MAY be used, as described in Appendix F of [[RFC7515]].

The typ header parameter SHOULD be vc-ld+jwt. @@ -304,7 +305,8 @@

Securing JSON-LD Verifiable Presentations with J

A [=conforming JWS issuer implementation=] MUST use [[RFC7515]] to secure this media type. - The unsecured verifiable presentation is the unencoded JWS payload. + The unsecured [=verifiable presentation=] is the unencoded JWS payload. + A detached payload MAY be used, as described in Appendix F of [[RFC7515]].

The typ header parameter SHOULD be vp-ld+jwt. @@ -453,10 +455,11 @@

Securing JSON-LD Verifiable Credentials with SD-JW

A [=conforming SD-JWT issuer implementation=] MUST use [[[SD-JWT]]] [[SD-JWT]] to secure - this media type. The unsecured [=verifiable credential=] is the input JSON - claim set. The Issuer then converts the input JSON claim set (i.e., the + this media type. The unsecured [=verifiable credential=] is the input + JWT Claims Set. The Issuer then converts the input JWT Claims Set (i.e., the unsecured [=verifiable credential=]) into an SD-JWT payload according to SD-JWT issuance instructions. + A detached payload MAY be used, as described in Appendix F of [[RFC7515]].

The typ header parameter SHOULD be vc-ld+sd-jwt. @@ -519,7 +522,8 @@

Securing JSON-LD Verifiable Presentations with SD-J

A [=conforming SD-JWT issuer implementation=] MUST use [[SD-JWT]] to secure this media type. - The unsecured verifiable presentation is the unencoded SD-JWT payload. + The unsecured [=verifiable presentation=] is the unencoded SD-JWT payload. + A detached payload MAY be used, as described in Appendix F of [[RFC7515]].

The typ header parameter SHOULD be vp-ld+sd-jwt. @@ -618,7 +622,8 @@

Securing JSON-LD Verifiable Credentials with COS

A [=conforming COSE issuer implementation=] MUST use COSE_Sign1 as specified in [[RFC9052]] to secure this media type. - The unsecured verifiable credential is the unencoded COSE_Sign1 payload. + The unsecured [=verifiable credential=] is the unencoded COSE_Sign1 payload. + A detached payload MAY be used, as described in Section 4.1 of [[RFC9052]].

The typ header parameter, as described in COSE "typ" (type) Header Parameter, SHOULD be application/vc-ld+cose. @@ -672,7 +677,8 @@

Securing JSON-LD Verifiable Presentations with C

A [=conforming COSE issuer implementation=] MUST use COSE_Sign1 as specified in [[RFC9052]] to secure this media type. - The unsecured verifiable presentation is the unencoded COSE_Sign1 payload. + The unsecured [=verifiable presentation=] is the unencoded COSE_Sign1 payload. + A detached payload MAY be used, as described in Section 4.1 of [[RFC9052]].

The typ header parameter SHOULD be application/vp-ld+cose. @@ -2349,9 +2355,9 @@

Algorithm for Verifying a Credential or Presentation Secured Set mediaType to vc
  • - Convert the SD-JWT payload back into the JSON claim set by reversing the process - in [[[SD-JWT]]] [[SD-JWT]]. Set document to the JSON claim set. - (For examples of the transition from JSON claim set to SD-JWT payload, please + Convert the SD-JWT payload back into the JWT Claims Set by reversing the process + in [[[SD-JWT]]] [[SD-JWT]]. Set document to the JWT Claims Set. + (For examples of the transition from JWT Claims Set to SD-JWT payload, please see SD-JWT examples).