Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

160 Connection can't complete with credo with no inbound transports #2041

Open
nodlesh opened this issue Sep 20, 2024 · 0 comments
Open

160 Connection can't complete with credo with no inbound transports #2041

nodlesh opened this issue Sep 20, 2024 · 0 comments

Comments

@nodlesh
Copy link

nodlesh commented Sep 20, 2024

I have a test where credo/acme requests mediation from an acapy/bob agent. On credo the inbound transports are not set but the outbound is set to "ws", "http" . The acapy agent has those settings for both inbound and outbound transports. It starts off trying to create a 0160 connection between the two agents, however, the connection never gets completed. The acapy connection state is responded while credo can’t determine the state. Somewhere along the way in the testing this was allowed to pass if afj/credo couldn’t determine the state, so I don’t know how long this has been happening. After the connection the test is requesting mediation from acapy with the connection id, which of course fails.
If I set the inbound transport for credo to "ws", "http" as well, then the connection completes fine and request mediation happens successfully. However the test is written in a way that it is expected to work when the inbound transports are not set. And this test was setup to run with AFJ with ACA-Py Can anyone shed some light on what might be going on here?
I do know that not all agent support being started without inbound transports, is this just a mistake and credo should not be running this test? The Credo docs seem to indicate that inbound transports are optional. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant