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
With anoncreds specifically. If faber issues multiple credentials to alice of the same type and then revokes any of the credentials, the next proof request will fail verification.
Steps (using demo):
start faber ./run_demo run faber --wallet-type askar-anoncreds --revocation
start alice ./run_demo run alice --wallet-type askar-anoncreds
connect
issue 3 credentials to alice
revoke credential 2
request proof
result will be verified = false
Screencast.from.2024-05-07.09.39.59.AM.webm
The text was updated successfully, but these errors were encountered:
jamshale
changed the title
Revoking one credential of many of the same type fails proofAnoncreds Revoking one credential of many of the same type fails proof
May 7, 2024
Sounds like this is either a bug in ACA-Py’s selection of a default credential to use when there are multiple — should choose the most recent non-revoked one, or in Alice picking the wrong one to use from a set.
That said, I don’t know how “default” is defined by ACA-Py. Presumably it is the first in the array of candidate VCs that could be used to satisfy the request.
With anoncreds specifically. If
faber
issues multiple credentials toalice
of the same type and then revokes any of the credentials, the next proof request will fail verification.Steps (using demo):
./run_demo run faber --wallet-type askar-anoncreds --revocation
./run_demo run alice --wallet-type askar-anoncreds
verified = false
Screencast.from.2024-05-07.09.39.59.AM.webm
The text was updated successfully, but these errors were encountered: