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
Current state:
Inviter throws exceptions when receiving connection requests to explicit public Out-Of-Band invitations, when there is more than one explicit public Out-Of-Band invitation in state invitation. The connection isn't established and stays in state invitation.
Desired state:
Inviter can create multiple explicit public Out-Of-Band invitations and invitees can receive them when they want to, without exceptions in the inviter.
Details:
When creating an invitation with public_did=true, the inviter will create a database entry for a connection with field invitation_key = public_did.verkey (see outofbound manager #L247). When providing multiple invitations, the inviter will have multiple invitations with the same invitation_key (and initially the same state invitation). If now an invitee receives one of the invitations, the inviter will run into an StorageDuplicateError in didexchange manager #L396.
If I understand the code correctly, fixing this would need some adjustments on how the didexchange manager correlates a received request to a previously created invitation.
The text was updated successfully, but these errors were encountered:
Current state:
Inviter throws exceptions when receiving connection requests to explicit public Out-Of-Band invitations, when there is more than one explicit public Out-Of-Band invitation in state
invitation
. The connection isn't established and stays in stateinvitation
.Desired state:
Inviter can create multiple explicit public Out-Of-Band invitations and invitees can receive them when they want to, without exceptions in the inviter.
Details:
When creating an invitation with
public_did=true
, the inviter will create a database entry for a connection with fieldinvitation_key = public_did.verkey
(see outofbound manager #L247). When providing multiple invitations, the inviter will have multiple invitations with the sameinvitation_key
(and initially the same stateinvitation
). If now an invitee receives one of the invitations, the inviter will run into anStorageDuplicateError
in didexchange manager #L396.If I understand the code correctly, fixing this would need some adjustments on how the didexchange manager correlates a received request to a previously created invitation.
The text was updated successfully, but these errors were encountered: