Skip to content
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

Open
coolbung opened this issue Jan 10, 2024 · 6 comments
Open

Multi-tenant (multi NP) support #61

coolbung opened this issue Jan 10, 2024 · 6 comments
Labels
enhancement New feature or request protocol server protocol server

Comments

@coolbung
Copy link

coolbung commented Jan 10, 2024

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.

  1. Each NP is served via a different DNS domain / subdomain
  2. There should be a configuration that maps the DNS domains/subdomains to the network configuration (keys, subscriber id, webhook etc) of the NPs
  3. The protocol server should be refactored such that depending on the domain/subdomain the request is coming from, the appropriate configuration should be injected for that request lifecycle
@coolbung
Copy link
Author

@bharath-ganapathy
Copy link

@sareenEminds Could you please check if this feature could be bumped up in our backlog? Could be useful in multiple networks coming up

@faizmagic
Copy link
Contributor

@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

@faizmagic faizmagic added the enhancement New feature or request label Jan 30, 2024
@faizmagic faizmagic added the protocol server protocol server label Apr 16, 2024
@vinod303
Copy link

vinod303 commented Jul 5, 2024

#51 #51 (comment)

@emmayank
Copy link

Hi @vbabuEM , can you check if this can be taken in backlog

thanks
@emmayank

@vbabuEM
Copy link
Contributor

vbabuEM commented Sep 24, 2024

@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
cc @vinod303 @faizmagic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request protocol server protocol server
Projects
None yet
Development

No branches or pull requests

6 participants