Closed ianco closed 2 weeks ago
Is this using the new present-proof 2.0 protocol? I wonder if some data structure changed slightly enough to require new mappings (that would be the easy option)...
It could be related to a cange to using the 2.0
protocol, I didn't really dig into it too much ...
Credential verification is working in production OrgBook but not locally.
Upon inspection the self-connection isn't getting created on startup (the OrgBook agent makes a connection to itself in order to ask itself for a proof).
This should happen on startup in this code: https://github.com/bcgov/aries-vcr/blob/main/server/vcr-server/app-vonx.py
... which it looks like doesn't get run any more ...
Closing as we're not planning to fix this issue. If a new instance is setup the self-connection (required for credential verification) has to be setup manually.
in prod, the "verification" page doesn't show the "claims proven.
Tested locally and I'm getting the following error: