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
accept_invitation for invitee current will succeed even if the DID within the Public DID invitation is invalid. This is because the implementation for into_did_doc will assume a default service of AriesService::default(), which is full of dummy data, and then that default is used in the case that resolving the DID from the ledger fails...
accept_invitation
for invitee current will succeed even if the DID within the Public DID invitation is invalid. This is because the implementation forinto_did_doc
will assume a default service ofAriesService::default()
, which is full of dummy data, and then that default is used in the case that resolving the DID from the ledger fails...Default logic found here; https://github.com/hyperledger/aries-vcx/blob/main/aries_vcx/src/common/ledger/transactions.rs#L102
E.g.
will result in
InviteeConnection<Invited>
after accept_invitation, and the did_doc will be:IMO it should just fail to accept if the diddoc cannot be properly resolved
The text was updated successfully, but these errors were encountered: