-
Notifications
You must be signed in to change notification settings - Fork 17
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
Multi-tenant (multi NP) support #61
Comments
@sareenEminds Could you please check if this feature could be bumped up in our backlog? Could be useful in multiple networks coming up |
@bharath-ganapathy , Let me review this request and get back |
@emmayank Sure. It can be picked up. It requires approval from Ravi and Faiz. This is a big change and I am not sure if they want to pick it up in the reference implementation |
Right now the protocol server can be configured with the credentials of a single NP.
We are using the Protocol Server in a SaaS service, and today we have to run separate pairs (one client mode + one network mode) of the protocol server for each NP that we host. We want to be able to run only one pair for all the NPs we host.
I'm proposing a design to handle the multi-tenancy at a DevOps level.
The text was updated successfully, but these errors were encountered: