OpenId4VP defines that vp_token could carry a single or multiple verifiable presentations.
Multiple presentations are being represented as an array where each element (presentation) is either a String or a JSON object.
Currently, endpoint expects in the direct_post or direct_post.jwt endpoint a vp_token a string. UI must be updated to support the following:
[x] When multiple credentials are shared (vp_token is an array) all shared documents must be presented.
[x] When multiple credentials are shared in enveloped form (vp_token is a string) all enveloped documents must be presented.
OpenId4VP defines that vp_token could carry a single or multiple verifiable presentations. Multiple presentations are being represented as an array where each element (presentation) is either a String or a JSON object.
Currently, endpoint expects in the direct_post or direct_post.jwt endpoint a vp_token a string. UI must be updated to support the following: