Any Benefits to using Auth0 in Next-Auth?
Hey, currently working on an expo app that uses Auth0 for auth. Planning on using it aswell for the nextjs app. I was looking at next-auth, and it seems to provide functionality to use Auth0 as a provider.
Would there realistically be any benefits to using this? I feel like it would just be easier to use the
@auth0/nextjs-auth0 package, as next-auth just feels like an unnecessary middle man.
I do store additional data about users, i.e their products etc, and use prisma currently, but I dont strictly need next-auth for this.13 Replies
yes ignore next auth here
that is assuming you're fine with paying for auth0 which it seems like
next auth is just a free option (obv not entirely cuz storing users = server + db = money) but you dont pay for the service itself
yea,
used next auth in the past for a few projects and its been great
only reason for auth0 is coz its a react native app
altho im working on trying to get nextauth with expo working...
create-t3-turbo hasnt done it?
nope
working with julius to try get it working
wtf does the mobile app do there
is just a useless brick
yea lol
it can communicate with ur api via trpc
but thats about it for now
so you need to make an "adapter" for it?
i would assume thats all you'd need
Powered by next-auth: https://cln.sh/G5CwgW0Z
this is what julius got working
<#1068918318460837949>
maybe being allowed to make auth endpoints yourself through various next auth helper functions
but apple is very specific on their login auth flow
i mean im still early in development and can switch t o next auth if needed
but idk if using next auth over auth0 would bring any benefits
was that painfully slow cuz of dev mode or is it just painfully slow
just painfully slow i believe.
im gonna try get it working later today
Biggest hiccup will be apple login
I think for now I’ll stick with auth0