trustbloc / mediator Goto Github PK

The hub-router project will be used by issuer/rp adapters and edge-agent. Currently, these projects are using aries-agent-rest. Internally, the hub-router will use aries-go-sdk. The features of aries-agent-agent (not provided by aries-sdk) thats used by trustbloc components need to be present/exposed in hub-router.

The list includes:

• Support to Generate router invitation #8
• Support to configure transports (http and websocket) #13
• Support to configure databases #2
• BDD tests #17

Use didcomm v2 invitation and connection without didexchange.

Update based on messages defined at https://trustbloc.readthedocs.io/en/latest/blinded_routing.html#wallet-to-router-create-connection.

API to generate DIDComm invitation

part of #8

At the end of the bdd tests, this error is thrown, resulting in a panic. For now, it's been changed to log the error instead of doing a panic. This only started happening recently.

See https://dev.azure.com/trustbloc/hub/_build/results?buildId=12625&view=logs&j=f1be9c17-063a-5582-5bdf-706dd0ad19dd&t=e3f07ae1-820c-5956-2a5f-03f799173432 for the error

Update the build process to add multi-platform support for both arm64 and amd64.

#23 (comment)

RP should communicate with Issuer through Router, rather than calling directly and vice versa.

The Hub Router should have the ability to create a connection with third party (user facilitates the connection between issuer/rp and router).

The hub-router DIDComm API should perform following tasks.

• Get the DIDDoc of third party in the request
• Create new PeerDID Doc in hub-router for that particular connection
• Send this new PeerDID Doc in the response

Implementation:

• Implement #26
• BDD test #27

Support couchdb storage

• edgestore
• ariesstore

Related to #2

• Update golang version to v1.15
• Update golang-ci lint version
• Update aries/edge-core dependencies

Currently, Azure Pipelines are used for CI builds.

Breaking changes were pushed to aries framework go as part of following PRs:

• hyperledger-archives/aries-framework-go#2238
• hyperledger-archives/aries-framework-go#2245

The hub-router need to fix the breaking changes while upgrading.

• provide different endpoints for each approved route - is this possible?
• does the user need to register against a router before they can pre-approve routes?
  • no - the user introduces the router to the other agent
  • the user only needs a didexchange connection with the router

Based on trustbloc/wallet#478

Part of #8

#23 (comment)

Use messaging client from aries instead of messenger

BDD tests to demonstrate following capabilities

• DIDExchange with Router
• Route registration
• DIDExchange with 3rd party through registered router