[has-PR] `vp_formats_supported` server metadata in OpenID4VP underspecified
Clarify that the vp_formats_supported
server metadata in OpenID4VP should be expressed as following (PE v2 syntax)
"vp_formats_supported": {
"jwt_vc": {
"alg": [
"ES256K",
"ES384"
]
},
"jwt_vp": {
"alg": [
"EdDSA",
"ES256K"
]
},
"mdl_iso_cbor": {
"alg": [
"EdDSA",
"ES256"
]
}
}
Comments (9)
-
-
reporter Something like this? I am ok renaming alg with alg_values_supported
vp_formats_supported": { "jwt_vc": { "alg_values_supported": [ "ES256K", "ES384" ] }, "jwt_vp": { "alg_values_supported": [ "EdDSA", "ES256K" ] } }
-
reporter during Aug-11 SIOP call, comments were made that the above proposed structure is well suited to express alg_values_supported per credential format, since if we have a separate parameters
alg_values_supported
andformats_supported
, it is not clear alg values for which format. -
reporter - changed status to open
-
I think we need a structure similar to this in order to group related metadata items together. Without this structure and having a simple list of metadata items, it becomes impossible to know which of the metadata values go together without having an explosion of property names. For example, two metadata properties, one with two different credential formats supported and one with 3 different crypto algorithms supported does not indicate which credential format supports which of the crypto algorithms. But the nested structure above does do this.
-
reporter (duplicate of
#1572) -
reporter -
reporter -
reporter - changed status to resolved
PR #270 merged
- Log in to comment
Syntactically, we tend to use names like
id_token_signing_alg_values_supported
rather thanalg
.