-
Notifications
You must be signed in to change notification settings - Fork 14
Blog: How to Integrate Clerk with Supabase ( + One Better Choice) #390
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
base: master
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for gracious-clarke-e6b312 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
… show the app without clerk or supabase, just the base app we will be working with
…nd overall look at.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall this blog is really in-depth and well written!
A few small suggestions:
-
Mention a migration stratergy/ link to supertokens migration docs
-
So one of the main things we also want to emphasize is why supertokens can be the superior option
- Extensibility, supertokens allows you to override all auth logic/UI components to create custom flows/ match your unique auth flow requirements
- granular session control, you have complete control over session expiry, set custom lifetime for access and refresh tokens.
-
go into a little more detail about the attacks and how supertokens stops them, additionally adding internal linking to relevant supertokens resources/blogs we have written about the topics
Link to Google Doc
https://docs.google.com/document/d/1N9klZeULiXSXHOETAoy2RhwPg36T8XbO4YNbVWKvq8c/edit?tab=t.0
Checklist