-
Notifications
You must be signed in to change notification settings - Fork 537
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
[RELEASE]: Multi tenancy UI dashboard + account linking fixes + telemetry change to include websiteDomain + email verification claim change + extending jwks lifetime #1011
Comments
Dashboard issues
|
Thoughts on 20th july, 2024I also thought about how we can change the docs and flow so that by default, users dont have to init stuff on the frontend (pre built ui) and can go to the dashboard directly to start configuring the tenants and login methods. This is possible if we:
The issue with the above is that it breaks the flow of setting up:
So they get real feedback really late in the setup phase. As opposed to now, where in the first step is setup frontend, and then get to see the pre built UI immediately. Which is why we didn't go ahead with these changes |
📅 Checklist
Release order
includeInNonPublicTenantsByDefault
and email verification claimsincludeInNonPublicTenantsByDefault
and email verification claims🔶 Staging
Dev Tag
includeInNonPublicTenantsByDefault
in ProviderInputincludeInNonPublicTenantsByDefault
in ProviderInputOthers
with-multi-tenancy-ui
branch from rishabhpoddar/multi-tenancy-mfa to the main branch📚 Documentation (test site)
https://supertokens.com/docs/thirdpartyemailpassword/pre-built-ui/setup/backendWe should make backend setup first in the docs, and then frontend setup.In backend setup, we should only tell users to setup init, middleware, error handler -> visit dashboard login and configure tenant. This means we will have to enable all recipes by default in backend, which is OK i think.In frontend setup, we should always add useDynamicLoginMethod: true, and always init all recipes, so users just have to call init.https://supertokens.com/docs/mfa/backend-setupFor MFA, we should tell users to config via dashboard only, and for complex stuff, they can do via code.🔥 Production
💻 NPM and core release
📚 Documentation
Contents of running try.supertokens.com script:
The text was updated successfully, but these errors were encountered: