Fix: DIF proof proposal when creating bound presentation request [Issue#1687]

[shaangill025]

Signed-off-by: Shaanjot Gill [email protected]

• resolve present-proof v2 puts records to the storage it can't read back any more #1687
• So the validation for /present-proof-v2.0/send-proposal is working but the problem was that with auto_respond_presentation_proposal flag on it would create an invalid bound request from the proposal [input_descriptors was not enclosed in presentation_definition]. I am surprised that I didn't catch this earlier.
• @swcurran According to the RFC, the propose-presentation message only expects input_descriptors and no options [for challenge and/or domain]. With auto flag, there will be no opportunity to add a domain to the request, so I have updated the schema to allow options in the propose-presentation message. challenge is always required for verifying presentation, if options is not specified then it is randomly assigned.

[swcurran]

@andrewwhitehead -- please review and (hopefully) approve the PR.

@shaangill025 do we need a reminder about when to change (or at least check) the locked down Ursa dependency? Maybe I put something in my calendar for (when?) to check this?

[shaangill025]

@shaangill025 do we need a reminder about when to change (or at least check) the locked down Ursa dependency? Maybe I put something in my calendar for (when?) to check this?

Timo just mentioned in #1704 that 1.0.2 was released by mistake. I think we can leave it fixed to 1.0.1 until 1.0.3 release or if we hear otherwise.