Christian Bormann
Christian Bormann
I would not mandate the Request Object to be signed in the "generic" OpenID4VP spec, but I do see that there might be value in switching to pure JAR instead...
I didn't have time to properly think about this yet so take this with a grain of salt, but the first question I had when reading the proposed API call...
I agree, I think there is value / use-cases for attestations without a cryptographic key binding
This would be the relevant code: https://github.com/hyperledger/indy-plenum/blob/ubuntu-20.04-upgrade/plenum/server/consensus/ordering_service.py#L1998-L2010
An easy first step could be to design a protocol or a small extension to the proximity flow in 18013-5 and demonstrate that it would also work presenting a second...
I'd like to bump this discussion before we go to 1.0 - now is a good time to simplify and there are a few breaking changes happening anyway. The issue...
I will create a PR soonish if no-one is objecting. I think this is a worthwhile simplification and we should introduce it rather soon.
This sounds like John should be there as well imho - If I recall correctly we had some initial discussions in this/a similar direction at an IIW with him?
I'd say it can be closed
Looks good to me with the changes! I guess we should not merge this until the Query Language PR is merged so it doesn't break the github action (vp_query reference)?