Skip to content

Commit 4bf0c65

Browse files
authored
Merge pull request #171 from oauth-wg/c2bo/sd-jwt-example
sd jwt example
2 parents 1482e02 + 8041023 commit 4bf0c65

File tree

1 file changed

+50
-2
lines changed

1 file changed

+50
-2
lines changed

draft-ietf-oauth-status-list.md

Lines changed: 50 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -326,9 +326,9 @@ The following is the CBOR Annotated Hex output of the example above:
326326

327327
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.
328328

329-
## Referenced Token in JWT Format {#referenced-token-jwt}
329+
## Referenced Token in JOSE Format {#referenced-token-jwt}
330330

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.
332332

333333
The following content applies to the JWT Claims Set:
334334

@@ -360,6 +360,53 @@ The following is a non-normative example for a decoded header and payload of a R
360360
}
361361
~~~
362362

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:
366+
367+
~~~ ascii-art
368+
369+
eyJhbGciOiAiRVMyNTYiLCAidHlwIjogImV4YW1wbGUrc2Qtand0In0.eyJfc2QiOiBb
370+
Ikh2cktYNmZQVjB2OUtfeUNWRkJpTEZIc01heGNEXzExNEVtNlZUOHgxbGciXSwgImlz
371+
cyI6ICJodHRwczovL2V4YW1wbGUuY29tL2lzc3VlciIsICJpYXQiOiAxNjgzMDAwMDAw
372+
LCAiZXhwIjogMTg4MzAwMDAwMCwgInN1YiI6ICI2YzVjMGE0OS1iNTg5LTQzMWQtYmFl
373+
Ny0yMTkxMjJhOWVjMmMiLCAic3RhdHVzIjogeyJzdGF0dXNfbGlzdCI6IHsiaWR4Ijog
374+
MCwgInVyaSI6ICJodHRwczovL2V4YW1wbGUuY29tL3N0YXR1c2xpc3RzLzEifX0sICJf
375+
c2RfYWxnIjogInNoYS0yNTYifQ.-kgS-R-Z4DEDlqb8kb6381_gHHNatsoF1fcVKZk3M
376+
06CrnV8F8k9d2w2V_YAOvgcb0f11FqDFezXBXH30d4vcw~WyIyR0xDNDJzS1F2ZUNmR2
377+
ZyeU5STjl3IiwgInN0cmVldF9hZGRyZXNzIiwgIlNjaHVsc3RyLiAxMiJd~WyJlbHVWN
378+
U9nM2dTTklJOEVZbnN4QV9BIiwgImxvY2FsaXR5IiwgIlNjaHVscGZvcnRhIl0~WyI2S
379+
Wo3dE0tYTVpVlBHYm9TNXRtdlZBIiwgInJlZ2lvbiIsICJTYWNoc2VuLUFuaGFsdCJd~
380+
WyJlSThaV205UW5LUHBOUGVOZW5IZGhRIiwgImNvdW50cnkiLCAiREUiXQ~WyJRZ19PN
381+
jR6cUF4ZTQxMmExMDhpcm9BIiwgImFkZHJlc3MiLCB7Il9zZCI6IFsiNnZoOWJxLXpTN
382+
EdLTV83R3BnZ1ZiWXp6dTZvT0dYcm1OVkdQSFA3NVVkMCIsICI5Z2pWdVh0ZEZST0NnU
383+
nJ0TmNHVVhtRjY1cmRlemlfNkVyX2o3NmttWXlNIiwgIktVUkRQaDRaQzE5LTN0aXotR
384+
GYzOVY4ZWlkeTFvVjNhM0gxRGEyTjBnODgiLCAiV045cjlkQ0JKOEhUQ3NTMmpLQVN4V
385+
GpFeVc1bTV4NjVfWl8ycm8yamZYTSJdfV0~
386+
~~~
387+
388+
Resulting payload of the example above:
389+
390+
~~~ ascii-art
391+
392+
{
393+
"_sd": [
394+
"HvrKX6fPV0v9K_yCVFBiLFHsMaxcD_114Em6VT8x1lg"
395+
],
396+
"iss": "https://example.com/issuer",
397+
"iat": 1683000000,
398+
"exp": 1883000000,
399+
"sub": "6c5c0a49-b589-431d-bae7-219122a9ec2c",
400+
"status": {
401+
"status_list": {
402+
"idx": 0,
403+
"uri": "https://example.com/statuslists/1"
404+
}
405+
},
406+
"_sd_alg": "sha-256"
407+
}
408+
~~~
409+
363410
## Referenced Token in CWT Format {#referenced-token-cwt}
364411

365412
The Referenced Token MUST be encoded as a "COSE Web Token (CWT)" object according to {{RFC8392}}.
@@ -868,6 +915,7 @@ for their valuable contributions, discussions and feedback to this specification
868915

869916
-04
870917

918+
* add sd-jwt-vc example
871919
* fix CWT status_list map encoding
872920
* editorial fixes
873921
* add CORS considerations to the http endpoint

0 commit comments

Comments
 (0)