You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When receiving a problem report on a connection-less proof request, ACA-Py considers it unsupported and raises an exception (see here.
This seems incorrect, and prevents the correct handling of rejected proof-requests (the verifier would not be able to know that a proof was rejected, and why).
Handling of the problem report should likely update the exchange record to "abort" it, and emit an event/webhook with relevant data for a controller to be able to reconcile it with the outgoing request.
The text was updated successfully, but these errors were encountered:
Comparing receive_presentation to receive_problem_report, it looks like the handler just needs to be updated to pass None as the connection_id when there's no connection record.
When receiving a problem report on a connection-less proof request, ACA-Py considers it unsupported and raises an exception (see here.
This seems incorrect, and prevents the correct handling of rejected proof-requests (the verifier would not be able to know that a proof was rejected, and why).
Handling of the problem report should likely update the exchange record to "abort" it, and emit an event/webhook with relevant data for a controller to be able to reconcile it with the outgoing request.
The text was updated successfully, but these errors were encountered: