This is a contributors guide and NOT a user guide. Please visit these docs if you are using or evaluating SuperTokens.
Multitenancy as a separate recipe
This is just a proposal so far, it hasn't been accepted and needs further discussion.
- rishabhpoddar, sattvikc
- Proposed by:
#Context and Problem Statement
To support the management of dynamic config, such as thirdparty provider list for each tenant, SDK must expose a set of management functions, to create, update, etc.
These functions are specific to each recipe. As an example, for thirdparty, we would need functions like:
- so on
Should these functions be exposed from individual recipes or a common
- Exposed via individual recipes
- Exposed via
Chosen option: Exposed via Multitenancy recipe, because
- Avoids duplication of the management functions. For example, thirdparty and thirdpartyemailpassword would expose same set of functions for the config management.