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

Switch to clerk for auth? #85

Open
louisunlimited opened this issue Jul 19, 2023 · 3 comments
Open

Switch to clerk for auth? #85

louisunlimited opened this issue Jul 19, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@louisunlimited
Copy link
Member

Next Auth seems kinda unstable and I'm now questioning stability when pushed to production. We've sure all experienced setbacks when using it in dev, for ex this:
Screenshot 2023-07-19 at 13 17 38

So here I propose using a third party auth service like Clerk.dev. It's free for < 5000 MAUs, which I think is pretty reasonable, and I've used it myself when building CS411 project and it seems reliable.

@RaymondWHZ @HaiyueZhang @pastezzz Thoughs?

@louisunlimited louisunlimited added the question Further information is requested label Jul 19, 2023
@RaymondWHZ
Copy link
Member

The concept of this product is excellent. In this way, we can allow users to register by email directly as they wish, and maybe it can provide a better way to manage SSO providers and users.

The question is: how does it store user information? On its own platform? Besides, how should we change our current session feature and database adaptor?

@louisunlimited
Copy link
Member Author

louisunlimited commented Aug 24, 2023

The concept of this product is excellent. In this way, we can allow users to register by email directly as they wish, and maybe it can provide a better way to manage SSO providers and users.

The question is: how does it store user information? On its own platform? Besides, how should we change our current session feature and database adaptor?

@RaymondWHZ Yes! We will let Clerk to handle all the storing/auth-ing of user info. We will need to remove all our db adapters and stuff form our current project since we don't need them anymore. So after this our db will be ONLY used for storing actual event logistics and such.

@RaymondWHZ
Copy link
Member

The concept of this product is excellent. In this way, we can allow users to register by email directly as they wish, and maybe it can provide a better way to manage SSO providers and users.
The question is: how does it store user information? On its own platform? Besides, how should we change our current session feature and database adaptor?

@RaymondWHZ Yes! We will let Clerk to handle all the storing/auth-ing of user info. We will need to remove all our db adapters and stuff form our current project since we don't need them anymore. So after this our db will be ONLY used for storing actual event logistics and such.

Great! I think we can proceed with this idea.

@louisunlimited louisunlimited added enhancement New feature or request and removed question Further information is requested labels Aug 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants