Closed
Description
Questions
- Can you easily add a custom social provider?
- How well do they support various platforms and SDKs?
- How can we go about customising the UI? From colours to full customisation
- How do we do things like handle sign up success?
- Social account consolidation?
- Can sessions be used with httpOnly cookies?
- Setting up for the two use cases of multi tenancy?
- If one needs to do something like paginating across all users in the app in their API, how can they do that?
- If someone wants to tweak the sign up / sign in APIs, how can they do that?
- How would adding custom sign up fields work?
- How would adding custom sign up validators work?
- Describe the dev setup experience (how many steps and what are they + time overall)
- How do go about sending emails yourself if you want to?
- How to go about customising the email design and or the sender's domain?
- How to implement sign out functionality?
- How to implement revoking a user's session functionality?
- What if you want to embed the sign up / in page into your website UI (As opposed to opening a new tab..). Is that possible?
- Will their solution work with serverless env like in nextjs or netlify?
- Email verification with Social providers, how does it work
- Changing Email for social provider, how it works
- if you want to add a password strength meter to registration, how does it work
- User has multiple sessions, only want to revoke a couple of them, how does that work
- For social account consolidation, how does changing the email work.
- Multi tenancy, properly how it works, redirection works with the frontend
- RBAC, check properly, how to get the role of the user within the API for custom logic for both frontend and backend.
- How to set roles for a user on backend, set multiple roles for a user.
- Documentation review
- Changing password validation(or some similar feature) for sign up does this get propagated to other places(Signin, password reset)
- what are the supported databases
- In multi-tenancy, can you share cookies between subdomains
- Is there a mechanism for protecting routes (similar to the supertokens auth wrapper). How easy is it to protect multiple pages and what does the code look like?
- If a session expires is there a pop-up? does the user have to handle it?
- mobile implementation, IOS and Android
- Email is not verified but password reset is done, does that verify email?
- implementation with ssr
- Migration to and away
- API customisability
- sharing session across sub domains
- How to disallow sign up and only have sign in?
Metadata
Metadata
Assignees
Labels
No labels