Auth handling at next.js vs at backend
Unanswered
Masai Lion posted this in #help-forum
Masai LionOP
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
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