Mobile Backchannel support for other frameworks besides Aca-py

[nodlesh]

Mobile backchannel rework to integrate with other Aries frameworks. Right now the Mobile Backchannel is an ACA-Py Backchannel

The mobile backchannel is just a backchannel that captures test calls to the Holder and does mobile things like display a QR code and wait for scanning. In theory, this already allows for other frameworks to act as Issuer and Verifier. It has been tried and there are issues when doing this with other frameworks besides Aca-py. Investigation is required to nail down the exact issues with the other backchannels/frameworks when used in the context of the Mobile Tests. It may be that this ticket breaks out into specific issues for each framework backchannel to fix issues there.

Proposal:
Need to refactor the Mobile Backchannel to be a facade/interface over any existing backchannel.

Have a command line option that makes one of the used agents a mobile agent, which places the facade over that backchannel and does mobile "things", like wait for QR code scanning, etc.

Tasks:

• Implement specific OOB tests that do Connection reuse and no reuse. Please add a specific test of OOB "connection reuse" #557
• Enable OOB in the Mobile backchannel
• OOB with attached Credentials? Is this implemented anywhere in any framework?
• Run the Mobile backchannel with other frameworks that match the holder role for AIP 1.0 level protocols.
• All tests with MobileTest needs the connection steps changed to match a more mobile friendly flow.
• Document and break out the issues with each framework into their own GitHub issues.

[nodlesh]

There might be an issue with Dotnet not getting the Credential.

AFJ can receive the credential but no presentation request.
Sends connections too fast(at the same time) so you don't get the verifier connection.

Maybe changing the flow of The connection steps in the feature file may get us close to having other frameworks working with the mobile backchannel.

[PatStLouis]

I submitted PR #586 addressing the second task of this issue.

After changing the order of the connection, I was able to successfully complete a mobile test with a combination of acapy/javascript/mobile backchannels in different roles.

Dotnet is still giving me an issue I was however able to further investigate what was the issue and its related to the timeout after sending an invitation. It marks the step as failed 5 seconds after sending the invitation. By the time the QR code is displayed on the terminal it is already too late an instantly fails, preventing the rest of the scenario to complete.

To fix this the dotnet backchannel will need a longer timeout before marking the connection as failed.

Currently unable to build afgo backchannel.

[nodlesh]

Thanks Patrick, this is great news. Did you attempt to try those tests with reordered steps with non-mobile backchannels? If not, I'll see if I can try it with your changes later today.

[PatStLouis]

I didn't test it with non-mobile backchannel myself. However the PR did test it as a check, here's the job details.

[PatStLouis]

I identified 3 issues with other backchannels:

• Dotnet: Invitation timeout is too low, by the time the QR code displays, the step is already failed.
• AFGO: Cannot build backchannel.
• Aries-VCX: Invalid invitation data (missing @type property (wallet just saves the qr code as a card) and wrong serviceEndpoint (local ip instead of public endpoint))

[2byrds]

Great work guys! I'll try to track along with your changes so that in the future I can contribute to the solution.

[swcurran]

• The .NET issue can presumably be fixed in AATH? @nodlesh is that something you can do?
• I've raised an issue (that is not being addressed) on AFGo about the build problem. All of the AFGo tests are currently failing in the nightly run -- the build failure for afgo-interop with other Aries Frameworks and now all of the AF-Go to AF-Go tests.
• It would be good for someone to raise an issue in Aries VCX about the issue.