Open pstuermlinger opened 4 years ago
I've just realized that the Toolbox lists OSMA as an "invisible" connection because there's no label transmitted. When I click on the pending connection without label, the following connection details are shown:
{
"their_did": null,
"my_did": null,
"label": null,
"connection_id": "43077766-1065-4a6b-9eb6-8b59334b2700",
"raw_repr": {
"accept": "auto",
"invitation_mode": "once",
"invitation_key": "EY1nZSa3UCVSChwKjVYiwAfyM385iY4WBFwtfiZ6sjc1",
"alias": "Galaxy",
"routing_state": "none",
"initiator": "self",
"connection_id": "43077766-1065-4a6b-9eb6-8b59334b2700",
"their_role": "",
"state": "invitation",
"updated_at": "2020-10-08 08:27:41.345756Z",
"created_at": "2020-10-08 08:27:41.345756Z"
},
"state": "pending",
"role": ""
}
Also, it works with the Trinsic counterpart. However, it's still not possible to establish a connection to a toolbox agent (auto-accept enabled). Toolbox-Agent to Toolbox-Agent is working like a charm.
@pstuermlinger Hello. I am facing a similar issue. I changed the line for pool to options.PoolName = "bcovrin-test" and tried to use this email verification service: https://email-verification.vonx.io/. But connection is stuck in Negotiating.
Hi,
I tried to connect OSMA with other agents. The first one was a dev-agent from trinsic, the other one a Toolbox demo agent.
Both connections remain in state "Negotiating". Is that because of an incomplete implementation in OSMA, a bug or some kind of configuration failure on my side?