Closed WadeBarnes closed 4 years ago
Here are the error logs with debug logging. Testing performed in the test
environment using https://test.orgbook.gov.bc.ca/api/credential/5/verify
.
Found this in the Indy channel about nonces beginning with 0 being a problem - https://chat.hyperledger.org/channel/indy?msg=ewszhz5mxpno3xfDx
Noticed that the error log above has a nonce beginning with a 0 (or two).
Credential verification can fail frequently with the following error in the API.
Uptime robot is indicating downtime on credential verification calls due to the above error. The call to
https://orgbook.gov.bc.ca/api/credential/5/verify
for example will return 200 regardless of whether the verification fails or succeeds, but when it fails it does not return the verification results that the monitor is looking for, instead it returns error results. A subsequent call to the same URL returns the expected verification results. Making it appear as though the reported downtime is a false positive.Example of the returned error message:
This issue can be reproduced by repeatedly requesting the same verification over and over (
Ctrl-F5
). The error will between every 3 to 20 refreshes.The issue is occurring in
dev
,test
, andprod
.