-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Password checker field in OAuth Login #3032
Labels
Milestone
Comments
68 tasks
@jywarren can please tell me what is the difference between the ruser and user? Which one do I need to migrate. The schema is as follows |
I think I need to migrate ruser. But I am not sure. |
That's right, we're trying to get rid of |
Sorry for late reply. I was sleeping at that time. Ok, I will send the migration of ruser. |
no problem!
…On Wed, Jul 18, 2018 at 7:27 AM Sidharth Bansal ***@***.***> wrote:
Sorry for late reply. I was sleeping at that time.
Ok, I will send the migration of ruser.
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3032 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ310yRU49sWBVg9gO9OBBpgM8Y6Cks5uHxuZgaJpZM4VJ2zn>
.
|
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please describe the problem (or idea)
A user creates an account by the legacy authentication system. The field password_checker is set as zero. Now he tries to login. The username will be taken. We will check if the user having this username has password_checker field as zero. Yes the user has it set as zero we will check if the password matches and logs him in.
Let us define the fields for provider
Facebook 1
Github 2
Google 3
Twitter 4
A new user creates his account using provider. Password checker will be initialised as mentioned above. Then an email is sent to his account to change the password. If the user resets his password then password checker field is set to zero.
Suppose he forgets to change his password. So it will be a non zero field until he resets his password.
Without resetting the password user tries to login with the username and password. He enters wrong password. Then the backend flow will be like follows. We will fetch the user from the username Then we will fetch the password checker field. We see that this is 1 that means the user has created his account via Facebook. So we will notify the user that he has to change his password by going to forget password.
We will set the field of all the existing users in our database as zero.
If the field is zero and a user links his account then the password checker field need not to be changed.
We don't have to do anything with the user tag model here. Just we need to migrate the user model.
Part of #2676
The text was updated successfully, but these errors were encountered: