Open peppelinux opened 3 weeks ago
We briefly discussed this on today's OpenID Connect WG call. These examples seem reasonable. What additional explanatory text do think should accompany them so that readers understand what's being illustrated by these examples?
We need to resolve how this works when the browser API is in use without requiring comparison of JSON (which has many of the same problems as canonicalisation of json). I don't think we should be adding things to the spec that only work when the browser API is not in use.
A solution would be to require that the necessary statements are passed in the OID4VP request by defining new parameters. I'm not sure this is the best way.
Leaving that aside, I'm also not sure how this works without the browser API - i.e. what you pass in oid4vp request.
RP Entity Configuration + Subordinate Statements adding authorized data in the request
Superior's Subordinate Statement