Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Detached payloads can be used #292

Closed
wants to merge 1 commit into from
Closed

Detached payloads can be used #292

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 16 additions & 10 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -250,7 +250,8 @@ <h2 id="securing-with-jose">Securing JSON-LD Verifiable Credentials with JOSE</h
</p>
<p>
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]].
</p>
<p>
The <code>typ</code> header parameter SHOULD be <code>vc-ld+jwt</code>.
Expand Down Expand Up @@ -304,7 +305,8 @@ <h2 id="securing-vps-with-jose">Securing JSON-LD Verifiable Presentations with J
</p>
<p>
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]].
</p>
<p>
The <code>typ</code> header parameter SHOULD be <code>vp-ld+jwt</code>.
Expand Down Expand Up @@ -453,10 +455,11 @@ <h2 id="securing-with-sd-jwt">Securing JSON-LD Verifiable Credentials with SD-JW
</p>
<p>
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
<a data-cite="SD-JWT#section-6.1">SD-JWT issuance instructions</a>.
A detached payload MAY be used, as described in Appendix F of [[RFC7515]].
</p>
<p>
The <code>typ</code> header parameter SHOULD be <code>vc-ld+sd-jwt</code>.
Expand Down Expand Up @@ -519,7 +522,8 @@ <h2 id="securing-vps-sd-jwt">Securing JSON-LD Verifiable Presentations with SD-J
</p>
<p>
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]].
</p>
<p>
The <code>typ</code> header parameter SHOULD be <code>vp-ld+sd-jwt</code>.
Expand Down Expand Up @@ -618,7 +622,8 @@ <h2 id="securing-vcs-with-cose">Securing JSON-LD Verifiable Credentials with COS
<p>
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]].
</p>
<p>
The <code>typ</code> header parameter, as described in <a data-cite="RFC9596#section-2">COSE "typ" (type) Header Parameter</a>, SHOULD be <code>application/vc-ld+cose</code>.
Expand Down Expand Up @@ -672,7 +677,8 @@ <h2 id="securing-vps-with-cose">Securing JSON-LD Verifiable Presentations with C
<p>
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]].
</p>
<p>
The <code>typ</code> header parameter SHOULD be <code>application/vp-ld+cose</code>.
Expand Down Expand Up @@ -2349,9 +2355,9 @@ <h3 id="alg-sd-jwt">Algorithm for Verifying a Credential or Presentation Secured
Set <code>mediaType</code> to <code>vc</code>
</li>
<li>
Convert the SD-JWT payload back into the JSON claim set by reversing the process
in [[[SD-JWT]]] [[SD-JWT]]. Set <code>document</code> 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 <code>document</code> to the JWT Claims Set.
(For examples of the transition from JWT Claims Set to SD-JWT payload, please
see <a data-cite="SD-JWT#appendix-A">SD-JWT examples</a>).
</li>
<li>
Expand Down
Loading