OpenID4VP
OpenID4VP copied to clipboard
openid
related to #156. 1. there have been conflicting comments whether type values should be "open-ended" so that e.g. each open banking jurisdiction for authorization of payments or data sharing and...
The current definition of the VP Token has two problems: (1) The current definition of the `vp_token` parameter is hard to read and the use of JSON is somewhat confusing:...
changes 'presentation_definition' descriptor to 'vp_token' for ac_vp_sd example
### Imported from AB/Connect bitbucket: https://bitbucket.org/openid/connect/issues/1814 ### Original Reporter: KristinaYasuda currently we just say that any client metadata can go into a `client_metadata` parameters, but I think parameters like `redirect_uris`,...
The current description in section 6.1. is tight to W3C VCs. Here is one example > The path_nested object inside an Input Descriptor Mapping Object is used to describe how...
When `client_id_scheme` is used, there can be multiple client_ids in the same ecosystem that belong to different clients. One of those clients could be malicious, compromised or the client_id scheme...
Related to #160, #161, #162 and #157. This is a proposal for a new query language fulfilling the requirements discussed in the issues linked above. I can create a PR...
fixes https://github.com/openid/OpenID4VP/issues/96.
There is an implicit understanding that parameters such as `nonce`, `client_id` and `client_id_scheme` are used in VPs but we don't have explicit language how this is done for specific format...
Is the satisfaction of the requirement expressed in the last sentence feasible? Especially in cases when the flow starts with a QR code scan? https://github.com/openid/OpenID4VP/blob/9a8ac76f93d0240767d92152085ae08c420d71cc/openid-4-verifiable-presentations-1_0.md?plain=1#L261
