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

Checklist to resolve issues for multi tenancy #756

Open
rishabhpoddar opened this issue Jul 26, 2023 · 0 comments
Open

Checklist to resolve issues for multi tenancy #756

rishabhpoddar opened this issue Jul 26, 2023 · 0 comments

Comments

@rishabhpoddar
Copy link
Member

rishabhpoddar commented Jul 26, 2023

  • In sub domain based login (where each tenant has their own sub domain), during development, if you are passing in localhost:3000 as the tenantId (which can happen if you are reading from the domain from getTenantId function on the frontend), then the paths to the backend will be like /auth/localhost:3000/... which will prevent our routing from matching any path. To solve this, users must use either a domain alias, or then return a different tenant ID in case the domain is localhost:3000.
  • The tenant that's currently trying to be used does not exist in the core
  • License key has not been added to the core.
  • If the third party provider array is not empty, and a tenant is loaded which has no providers configured for it, it will result in those providers being rendered which are specified in the providers array. So you should remove the providers array entirely.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant