I have an application where each client can have multiple users. Each client gets their own specific deployment of the application that runs in its own kubernetes pod. Currently, each client also maintains its own user database via the Parse open source system. We are in the process of migrating to leverage Auth0 for login purposes. When a user hits the app, they are hitting a url specific to the client instance ex:
I’m leveraging Auth0 lock to present the user with a login UX that we will be replicating against all of our other products. I’ve currently got a custom connection setup at the Auth0 application level, that uses a custom login script. The login script needs to be able to make a post request to the “client specific” parse endpoint. I would love to be able to know if there is a way to accomplish this without needing to setup a custom connection per client that we have (currently there are ~1000 users spread across ~300 unique clients - each client runs in its own kubernetes pod).
Currently I have a solution in place that works with a single client, as I have manually setup the connection and login script to make the post request to the specific client endpoint.
If I go the route of setting up a custom connection per client, are there limits to the number of custom connections that can be setup for a tenant?
Do you have any other recommendations as to how to go about implementing this. The current constraints are that we are not migrating the identity store to auth0, and as part of the “login” procedure, the Auth0 login scripts need to make a post request to the client specific Parse server.