Right now we are only able to exchange data one way between tax_advisor (consumer) and company (provider). We want to first of all implement it the other way around and also add the possibility to exchange the data with the third role, the bank
User story
As a tax advisor (:29191) , I am able to receive data / API endpoint from company (:19191) however I would like to able the send the data back to the company and also another role like bank (:39191) so that a multi way interaction is possible.
Acceptance Criteria
In the resources and dataplane directories, create all the necessary json file to ensure an data interoperability / interaction between three roles. (register-data-plane.json, create-policy.json, fetch-catalog.json etc.)
A single connector (example tax advisor) could receive but also send data using the same port 29191 and no need to create a new connector.
For now, it is enough to use the sample data, asset and policy from the connector tutorial.
If it is feasible, then dynamically create the json file, worst case scenario hard coded.
Right now we are only able to exchange data one way between tax_advisor (consumer) and company (provider). We want to first of all implement it the other way around and also add the possibility to exchange the data with the third role, the bank
User story
As a tax advisor (:29191) , I am able to receive data / API endpoint from company (:19191) however I would like to able the send the data back to the company and also another role like bank (:39191) so that a multi way interaction is possible.
Acceptance Criteria
DoD General Criteria