How to use a single protocol server for multiple participants and domains

[shiva-rakshith]

Can we use a single protocol server to support for multiple participants and domains?
In example, we have four domains under DSEP protocol (courses, scholarships, jobs and expert connect). When a participant is registered, they can choose only one network domain. If an org want to onboard onto four domains, they have to create four participants and run four instances of protocol server. Do we have an option to allow multiple participants to use the same protocol server?

[coolbung]

Multi-tenancy has been picked up by Tekdi and the team is testing it out. Request @suraj-tekdi and @vinod303 to share the implementation details for others to comment on.

[suraj-tekdi]

1. We have edited yaml file, and added details for each of the subscriber & added the subsciber configuration in forms of array. (sample show below)
   ` # Mandatory.
   keys:

   • privateKey: "Hgsk1389***********"
     publicKey: "Hgsk1389***********"
     uniqueKey: "123abc***"
     subscriberId: "bd1f-2409-40e5-95-5843-645a-6813-d18a-2129.ngrok-free.app"
     subscriberUri: "https://bd1f-2409-40e5-95-5843-645a-6813-d18a-2129.ngrok-free.app/" # ==========> localhost:5002

   • privateKey: "Hgsk1389***********"
     publicKey: "Hgsk1389***********"
     uniqueKey: "123ac****"
     subscriberId: "jobs-bap-dev.tekdinext.com"
     subscriberUri: "https://jobs-bap-dev.tekdinext.com/" # ==========> localhost:5002

   • privateKey: "Hgsk1389***********"
     publicKey: "Hgsk1389***********"
     uniqueKey: "123abc***"
     subscriberId: "smart-days-happen.loca.lt"
     subscriberUri: "https://smart-days-happen.loca.lt/" # ==========> localhost:5002`

2. We have edited the protocol-server file (src/middlewares/auth.middleware.ts, src/schemas/configs/app.config.schema.ts, src/utils/auth.utils.ts, src/utils/context.utils.ts, src/utils/telemetry.utils.ts) to get the subscriber id from the context & look the corresponding keys in the yaml file from the keys array and execution continues as before.

3. And forwarded all the bap network routing to one server as mentioned above (localhost:5002)

With the above change, we have currently tested the search transaction from different BAPs and getting the results as expected. Verified the transactionID, logs and concurrency and did not noticed any problems.
We will now continue the same for other transacitons and will update here @coolbung

[vinod303]

#61 #61