Open nodlesh opened 3 years ago
The expected behaviour is that if a non-revokable credential is selected to be used for a prove and the proof request has a revocation interval, the revocation interval should be dropped prior to the call to "indy_prover_create_proof". Note that the verifier will be able to tell if the proof SHOULD have included a proof of non-revocation by looking at the ledger, so this is safe to do.
Describe the bug A clear and concise description of what the bug is. This bug was identified in interoperability testing in Aries Agent Test Harness. A revocation test (T013-HIPE0011) that has Aries Framework Dotnet as the holder, and has a non-revocable credential used with a presentation that has a non-revocation interval.
To Reproduce To construct this scenario,
The results of this test can be seen at the AATH Interop Results page, https://allure.vonx.io/allure-docker-service-ui/projects/acapy-b-dotnet/reports/latest The tests can be executed locally by following the AATH execution instructions, https://github.com/hyperledger/aries-agent-test-harness
Negative Behavior When the SendProofPresentation happens the dotnet agent throws an indy error.
Revocation Registry Id not found
Full stack trace isExpected behavior According to Revocation RFC 441, it is to be expected that this scenario should pass. RFC 441 states,
A revocable or non-revocable credential may satisfy a presentation request with or without a non-revocation interval...