Open anubhav06 opened 2 years ago
Currently the required fields for Registration are:
Username, Password, Confirmation Password, Email, Mobile Number
and the user is logged in based on theirusername
andpassword
.The username fields needs to be removed as it's kind of redundant keeping in mind what this project is i.e. a food ordering web application (with no use of a username).
User authentication should be done based on the
password
rather thanusername
andpassword
.This will be similar to restaurant's authentication, where restaurant owner's are authenticated based on their
email and password
and no username is asked during login/registration
This can be done with Firebase, I believe. Don't know if you've heard about it.
I don't think firebase is necessary for this. This can be done very easily using Django in the backend only.
This will be similar to restaurant's authentication, where restaurant owner's are authenticated based on their email and password and no username is asked during login/registration
I don't think firebase is necessary for this. This can be done very easily using Django in the backend only.
This will be similar to restaurant's authentication, where restaurant owner's are authenticated based on their email and password and no username is asked during login/registration
Ok cool. As I mentioned in #20 , I haven't really gotten into Django because my computer can't handle it... Just curious, does django give a password reset link or something to reset password, from the back-end, like Firebase does?
I don't think firebase is necessary for this. This can be done very easily using Django in the backend only.
This will be similar to restaurant's authentication, where restaurant owner's are authenticated based on their email and password and no username is asked during login/registration
Ok cool. As I mentioned in #20 , I haven't really gotten into Django because my computer can't handle it... Just curious, does django give a password reset link or something to reset password, from the back-end, like Firebase does?
Yes, it does! That's one of the many things which I love about Django that it makes user authentication very simple!
We can either reset the password as an admin from the Django Admin Panel, or let the client reset their password themselves (by providing them with a password reset link)
Oh. Very interesting
On Mon, 21 Feb 2022 at 22:52, Anubhav Gupta @.***> wrote:
I don't think firebase is necessary for this. This can be done very easily using Django in the backend only.
This will be similar to restaurant's authentication, where restaurant owner's are authenticated based on their email and password and no username is asked during login/registration
Ok cool. As I mentioned in #20 https://github.com/anubhav06/eatit/issues/20 , I haven't really gotten into Django because my computer can't handle it... Just curious, does django give a password reset link or something to reset password, from the back-end, like Firebase does?
Yes, it does! That's one of the things which I love about Django that it makes user authentication very simple! We can either reset the password as an admin from the Django Admin Panel, or let the client reset their password themselves (by providing them with a password reset link)
— Reply to this email directly, view it on GitHub https://github.com/anubhav06/eatit/issues/14#issuecomment-1047095744, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUGJUTNLNTB2MXXPE6H4FRDU4JYHBANCNFSM5NXNDCJA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID: @.***>
Currently the required fields for Registration are:
Username, Password, Confirmation Password, Email, Mobile Number
and the user is logged in based on theirusername
andpassword
.The username fields needs to be removed as it's kind of redundant keeping in mind what this project is i.e. a food ordering web application (with no use of a username).
User authentication should be done based on the
email
andpassword
rather thanusername
andpassword
.This will be similar to restaurant's authentication, where restaurant owner's are authenticated based on their
email and password
and no username is asked during login/registration