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

Clerk Authentication Failing in Both Development and Production Environments #7

Open
sahil-idk opened this issue Jul 7, 2024 · 3 comments
Labels
question Further information is requested

Comments

@sahil-idk
Copy link
Owner

image

I just now came across this
Should we opt for other authentication services such as Lucia Auth or some other authentication toolkit ?
@Sahil-Sharma-23

Pls feel free to comment

@sahil-idk sahil-idk added the question Further information is requested label Jul 7, 2024
@Sahil-Sharma-23
Copy link
Contributor

image

I just now came across this Should we opt for other authentication services such as Lucia Auth or some other authentication toolkit ? @Sahil-Sharma-23

Pls feel free to comment

Yes. Instead of fully managed auth providers, we can use something like NextAuth.js to have much more control over the authentication process.
Check the below doc link to get started.
https://next-auth.js.org/getting-started/example

@sahil-idk
Copy link
Owner Author

The problem is that in next auth it has very minimal interface and also has build fails after a while , lucia on other hand gives flexibility of interface but the code is more . i personally had build fails in nextauth and also other projects made by yt creators was same on their deployed app

@Sahil-Sharma-23
Copy link
Contributor

In that case, we can then move ahead with lucia auth.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants