Authentication can be a bit sketchy sometimes as we have to keep so much in mind, like session management, protecting several routes/pages, hashing...
For further actions, you may consider blocking this person and/or reporting abuse
Well, i think not working with version 4 of next-auth
Thanks for the information, haven't looked into V4 yet. Will do and update :)
Do you know how to make it work with version 4?
Here you go github.com/DawnMD/next-auth-creden...
Do you know how to make it work with version 4?
Were you able to solve this?
I need to know how to connect with mongodb using version 4 too
Nice one bro, but my concern is that I already worked on a backend api which is on a separate codebase, I don’t want to bring in backend logic to my frontend. This doesn’t feels organised, structured or even secured
Hi, how can I encode more information in the cookies while signing in. In the above example you've shown, to encode email only(i.e. return {email: result.email}). How can
I for example save user address in cookies? I've tried (return { email: result.email, address: result.address}, but that didn't work.
By any chance is this on Github? As I am a little lost as to where the signup form sits.
Here you go github.com/DawnMD/next-auth-creden...
SyntaxError: Unexpected token < in JSON at position 0
npm i next-auth mongodb bycryptjs
should be:
npm i next-auth mongodb bcryptjs
thanks man :)
its not a secure way
please check typeof password and email
in youre way, password and email can be object or etc.