Auth handling at next.js vs at backend

[scenic pollen]

Any reason to handle auth at next.js over handling at backend Why can’t we just create the auth session directly on the api server ( by integrating auth0 with your api server) , and have browser sends the 🍪 automatically?

In other words, Next.js works as frontend framework. Authentication session is created at api/backend server (api.website.com) , and browser sends the cookies to identify the session automatically as that’s login response cookies are set on that domain

[lost brook]

Post created!

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize

✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)

[scenic pollen]

why use nextauth.js