A general way to do this is by taking a "token" from the login/signup request and store it in our database. The token will be stored in our user's table called Profile which is a table inheriting the django.contrib.auth.models.User table. This new table will contain the fields:
google_token
facebook_token
... etc
Additional Tasks
Provide a name for the register/ and login/ and any other routes you have created. Make sure the naming scheme is consistent.
Scope
Sign up and Sign in views.
register/- (unnamed)login/- (unnamed)Description
We need social sign-up/sign-in feature which enables users to register or login to our app using their social accounts such as Google, Facebook etc.
For now we will just go for Google social sign-up/sign-in.
References
Additional Information
A general way to do this is by taking a "token" from the login/signup request and store it in our database. The token will be stored in our user's table called
Profilewhich is a table inheriting thedjango.contrib.auth.models.Usertable. This new table will contain the fields:Additional Tasks
register/andlogin/and any other routes you have created. Make sure the naming scheme is consistent.