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: draft-ietf-oauth-status-list.md
+50-2Lines changed: 50 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -326,9 +326,9 @@ The following is the CBOR Annotated Hex output of the example above:
326
326
327
327
By including a "status" claim in a Referenced Token, the Issuer is referencing a mechanism to retrieve status information about this Referenced Token. The claim contains members used to reference to a status list as defined in this specification. Other members of the "status" object may be defined by other specifications. This is analogous to "cnf" claim in Section 3.1 of {{RFC7800}} in which different authenticity confirmation methods can be included.
328
328
329
-
## Referenced Token in JWT Format {#referenced-token-jwt}
329
+
## Referenced Token in JOSE Format {#referenced-token-jwt}
330
330
331
-
The Referenced Token MUST be encoded as a "JSON Web Token (JWT)" according to {{RFC7519}}.
331
+
The Referenced Token MAY be encoded as a "JSON Web Token (JWT)" according to {{RFC7519}} or other formats based on JOSE.
332
332
333
333
The following content applies to the JWT Claims Set:
334
334
@@ -360,6 +360,53 @@ The following is a non-normative example for a decoded header and payload of a R
360
360
}
361
361
~~~
362
362
363
+
SD-JWT-based Verifiable Credentials {{SD-JWT.VC}} introduce the usage of Status List in Section 3.2.2.2. The "status" object uses the same encoding as a JWT as defined in {{referenced-token-jwt}}.
364
+
365
+
The following is a non-normative example for a Referenced Token in SD-JWT-VC serialized form as received from an Issuer:
0 commit comments