Closed swcurran closed 1 year ago
@shaangill025 , when you get a chance, please take a look. @ianco -- FYI.
If you just use the menu option (option 1
to send a credential) then a single credential is issued and only a single credential is stored in Alice wallet
Looking into the instructions ...
I think when you use the /issue-credential-2.0/send
endpoint, because it automates the flow, you are getting the duplicate because the controllers are also responding to the webhooks. So for these instructions you should only use the /issue-credential-2.0/create-offer
endpoint (or else you should run alice and faber with the --no-auto
option.
@swcurran what's your preference?
If we turn off auto processing, the presentation process will be harder, right, since that will no longer be automated? The /send
on issue is kind of auto
on the fly.
The create-offer
sounds fine. It seems more confusing because we both have a controller and we have the --auto
in ACA-Py.
Anyway -- up to you. I don't have a preference as long as it works :-)
Closing
Steps to replicate the problem:
issuer
with Faber's did:keyid
incredentialSubject
with Alice's did:keyproofType
inoptions
withEd25519Signature2018
cred_id_stored
:Execute with an empty (
{}
) payload the Alice endpointPOST /credentials/W3C
and see that result shows an array of two credentials -- each the same.Shouldn't there just be one credential?
Assuming this is an issue, not sure if it is in ACA-Py (although I suspect it is) or the demo controller.