Next.js Discord

Discord Forum

Authentication Library Choices

Answered
Common paper wasp posted this in #help-forum
Open in Discord
Avatar
Common paper waspOP
So I don't know too much about what's out there for a certain area. I'm looking to add an OAuth login through GitHub and have been looking and researching different providers. I've come across

- NextAuth (through the docs)
- AuthJS (which I think NextAuth is built off of)
- Clerk
- Supabase Auth

I'm guessing for a Next project, deployed on Vercel (which is my plan), NextAuth would be the easiest and go-to in this instance but just wondering about the other options and pros and cons to each maybe? I'm not a developer or software engineer so I'm really blind with some of this stuff. Thanks in advance!
Answered by Common paper wasp
Ok finally figured it out. If you like something quick and easy to setup for a Next project with really good documentation, Clerk is a good fit. It was easy to setup, provides ways to customize and if you don't want to deal with setting up your own OAuth handlers/routes, then Clerk does it all for you. Very nice, A+
View full answer

30 Replies

Avatar
Siberian
I've only briefly tried it and not on a real project but from what I've heard Next Auth actually isn't fun to implement at all
altho that's mostly related to password/email login
the complaints I hear about it I mean
I'm personally using Supabase on a project right now and it's been nice
everyone seems extremely enthusiastic about Clerk too but obv that'll probably cost you money
Avatar
Common paper waspOP
Thanks for the response! I was looking at Clerk's docs and it looks like they had a generous free tier. But I looked the other night and I might be misremembering
Does Supabase provide a pretty easy OAuth implementation?
For providers like GitHub?
Avatar
Siberian
yeah
and yeah I think they recently actually improved their pricing a bit more
they also might have changed this but last time I used them you couldn't get rid of their branding on login screens etc when using the free tier
Avatar
Common paper waspOP
Supabase you mean?
Avatar
Siberian
that might be a dealbreaker for you
no Clerk
Avatar
Common paper waspOP
Ah let me take a looksie
Avatar
Siberian
or Supabase incase you mean the github one, cause yeah they do have that
again been a while but I think Clerk will def be easier to set up, but main advantages will come from stuff like roles/organisations and such
which can be a bit of a pain to set up yourself if you need it
Avatar
Common paper waspOP
Ahhhhh. Okay let me finally look at Clerk's pricing lmao
Got distracted with work
10000 monthly active users is all it says
I have a very small blog that will probably barely be used
I actually don't see anything in these docs about using OAuth
Oh there it is
Avatar
Common paper waspOP
Wow this is really easy to setup
Avatar
Lionhead
Spent at least a week on NextAuth and it's still buggy (ANd I have written auth libraries from scratch in the past, so I generally know what I am doing). Read this for some options: https://www.reddit.com/r/nextjs/comments/18olw72/nextauth_is_hell/
Avatar
Common paper waspOP
Lol noted. I'm going to try implementing Clerk in this project and see how it works for me. Again, I'm not making anything large enough to care about other factors like users or orgs or anything like that. Just simple OAuth implementation to allow people to post on a guestbook. That's it. Following Lee Rob's example
Because I have no ideas of my own lol
Avatar
Common paper waspOP
Ok finally figured it out. If you like something quick and easy to setup for a Next project with really good documentation, Clerk is a good fit. It was easy to setup, provides ways to customize and if you don't want to deal with setting up your own OAuth handlers/routes, then Clerk does it all for you. Very nice, A+
Answer
Avatar
Common paper waspOP
@Siberian Not to bring this up in a closed thread but I think im going to give Supabase Auth a shot. Clerk was just way too complex once you got to deploying it to PRD and I couldn't figure out CORS or CSP 😄