Hello! NextAuth is a great choice when it comes to adding authentication to your next.js app. And it's easy to see why, with it's vast coverage of ...
For further actions, you may consider blocking this person and/or reporting abuse
you can also set
redirect = false
and catch response fromsignIn
function :signIn
return a Promise which has following structure :you can check more on next-auth.js.org/getting-started/c...
Cool! Happy to see it has been added as a feature. Thanks for the update :)
Thank you so much! I hated that the function reloaded the page every time I submit the form
How does this work?
I have followed your example and am not getting any response in login page
You are not getting a response because the user isn't being set properly. The following code is able to handle Credentials (user & pass) and Providers auth, while setting jwt and session correctly.
Hi guys, if you need the token in an axios request, do it like this!
Hi guys, the article has gotten me as far as a successful authentication, for which am grateful. However, I am unable to get the session data using
getSession()
oruseSession()
client-side for which they both return null. What are the possible causes of the bug/issue?Have you added the Provider in your _app.js ?
for me it returns undefined.
Did you solve your problem? If yes, can you explain me how?
I would be interested in the HTML parts as well! do you have a zip of the shell project? I'm new to building React and Next applications from the ground up and find that most tutorials omit important details, making it very difficult to figure out what they are
Sure thing. I'll add the HTML part soon
Hello Twisha, I came here after one full days googling. I wanted to create a social media sign up button for a nextjs app with with what you call a custom laravel backend. The usage of ' pages/api/[..nextauth].js ' made me asking, where are they even using the custom backend .
So Just to confirm, even you have a custom backend you have to use pages/api feature in the app and define your auth providers there and call the custom backend api's from there right ?
Hey Bharath,
If you are using a third party provider for authentication i.e Google, Facebook, Apple, Twitter etc. you don't need a custom backend as everything will be handled by nextauth.js.
If instead you want to use email-passsword login where the credentials are sent to your custom backend (in this case I'm assuming your Laravel app) then you can use the Credentials provider and configure it as it is explained in the article.
For third party provider logins (google, facebook, twitter etc.) nextauth has good documentation. For example this one is for Google -> next-auth.js.org/providers/google
Overall all the configurations for next-auth is in the pages/api/[..nextauth].js file.
Hope it answers your question :)
What I actually wanted was to save the username, email ... fields after the google / signup to my own database. I think I figured it out. I am using the callbacks options inside the [...nextauth].js to call my api to pass username and email to my backend to store in my db.
Ah okay I see what you mean, thanks for sharing your solution :)
Hi there! Thank you for this very helpful article. I understand the login process, but how would you go about creating a custom registration page? Would you have to use the same 'authorize' callback that would have to hit different API endpoints (/login, /signup)? I would love to hear your thoughts on this :)
Please find this link.
dev.to/ekrresa/authenticating-with...
Thanks for sharing this.
Glad it helped! :)
Hi Twisha! Great article, thanks for the tips!
I'm wondering if there is a possibility to implement a OTP Login with NextAuth. I can't find anything on the internet 🤔 Do you have some advices?
Thank you! 🎩
Thanks Vlăduț Ilie !
Unfortunately I have not explored that option with NextAuth yet :(
Hope you find a useful solution soon :)
Muy útil ... mucha gracias!
Glad it's helpful :)
Hi Twisha, nice article. However the file to configure the providers should be pages/api/auth/[...nextauth].js NOT pages/api/auth/[...next-auth].js
That's correct! Thanks for catching that. Will update the article
Should we use session table in database for post our session?
this does not handle CSRF token. Could you please share how you would go about handling cross site request forgery?
THANK YOU SO MUCH !
Glad it helped! :)
You just absolutely saved me! First article I found which is dealing with own backend. 1000x thanks @twisha !
I'm so glad! :)
In the JWT callback you access the token inside user.data, isn't that not secure?
Can you share the source code of this article
Yup I have updated the article with a link!
This is great. but can you give me idea how to to that with sanity cms?