Normatively define how an SD-JWT VC is returned in vp_token - #782
Conversation
Specify that each SD-JWT VC presentation is a string containing an SD-JWT or SD-JWT+KB in the compact serialized format from Section 4 of the SD-JWT specification, and that the JWS JSON Serialization must not be used, as agreed in the working group discussion today. closes #780
|
Discussed on the APAC call today:
|
Agreed, this should imho go into 1.0 errata as well |
5085c8a to
0b35786
Compare
|
Both points resolved. I did actually mean to put it into 1.0 errata but forget. Then remembered and forgot again. So I agree it should be there. |
|
Discussion in group: We need to see if this is needed after #726. It may work to land this one anyway. |
Even if we reference a version of SD-JWT VC that includes the changes in https://github.com/oauth-wg/oauth-sd-jwt-vc/pull/425/changes I think we still need this text to make clear that, even if an ecosystem decides to fully define a JSON serialisation, that it needs to have a different credential format identifier than the compact serialisation. |
Specify that each SD-JWT VC presentation is a string containing an SD-JWT or SD-JWT+KB in the compact serialized format from Section 4 of the SD-JWT specification, and that the JWS JSON Serialization must not be used, as agreed in the working group discussion today.
closes #780