Closed ianco closed 9 months ago
Sorry — wrong comment previously — deleted.
It should be updated in AATH. In the AnonCreds spec, we neutralized the ID from explicitly being a DID to simply being being an ID.
OK I'll take a look at AATH, I expect we'll need to leave issuer_did
when running with askar
tho (askar-non-anoncreds
) ...
... actually I'll log an issue in AATH. This affects all the backchannels, depending on if we change the test cases, or we require each backchannel to understand what to do with issuer_did
vs issuer_id
...
I'm working on this in tandem with hyperledger/aries-agent-test-harness/issues/748 . They are both required to get the tests working.
Closing this ticket. The discrepancy it handled correctly internally and the only change that was needed in the test harness for this was to send a correct filters
payload with "filters": { "indy": {"cred_def_id": "replace_me"}}
.
In this method, the anoncreds issuer expects an
issuer_id
, however the AATH tests are passing in anissuer_did
:https://github.com/hyperledger/aries-cloudagent-python/blob/main/aries_cloudagent/anoncreds/issuer.py#L452
Should the anoncreds method in aca-py be updated to accept
issuer_did
or should the AATH backchannel be updated?AATH:
Stack trace: