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
{{ message }}
This repository has been archived by the owner on Mar 27, 2024. It is now read-only.
Integrated web KMS provided by trustbloc to the aries rest agent and tried creating a new connection, it got stuck at "requested" state and this error showed up in the agent: error: failed to unpack msg from ws: unpack
I actually want to use the web KMS as a common keystore for all the aries services running along with it so that I can route requests from one to another after connection establishment succeeds.
Expected result
It should move from "requested" state to "completed" state and did:key of this connection should be retrievable by the other aries services
Actual result
error: failed to unpack msg from ws: unpack
The text was updated successfully, but these errors were encountered:
What I'm trying to do
Integrated web KMS provided by trustbloc to the aries rest agent and tried creating a new connection, it got stuck at "requested" state and this error showed up in the agent: error: failed to unpack msg from ws: unpack
I actually want to use the web KMS as a common keystore for all the aries services running along with it so that I can route requests from one to another after connection establishment succeeds.
Expected result
It should move from "requested" state to "completed" state and did:key of this connection should be retrievable by the other aries services
Actual result
error: failed to unpack msg from ws: unpack
The text was updated successfully, but these errors were encountered: