Skip to content
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 and Email change strategies #23

Closed
keawade opened this issue Dec 13, 2015 · 4 comments
Closed

Password and Email change strategies #23

keawade opened this issue Dec 13, 2015 · 4 comments
Assignees

Comments

@keawade
Copy link
Collaborator

keawade commented Dec 13, 2015

I think we need to make users confirm email and password changes via email. For example, a user wants to reset their password so they click a reset password button on our site. The server then emails the user with a one time use reset token.

I think we should do the same with changing email addresses since someone could just crack a password, change the email, then get the change password token at the new email.

@NathanBland
Copy link
Contributor

I agree.

On Sat, Dec 12, 2015 at 11:33 PM, Keith Wade notifications@github.com
wrote:

I think we need to make users confirm email and password changes via
email. For example, a user wants to reset their password so they click a
reset password button on our site. The server then emails the user with a
one time use reset token.

I think we should do the same with changing email addresses since someone
could just crack a password, change the email, then get the change password
token at the new email.


Reply to this email directly or view it on GitHub
#23.

@NathanBland
Copy link
Contributor

So really, this should work for the forgot password link on our registration form, and for the change email in our settings on profile, however there are some problems.

One of the main reasons someone might change an email is if they lose access to that account, such as no longer being at a college, or job. In this case they would be locked out of their account, and since we don't have any other information on them, we would have no way to verify their identity if they contacted us for help.

I think we should experiment with other options here, such as just requiring two factor authentication for user settings. A simple text, or a second email address as a backup would work great for this.

@keawade thoughts?

@keawade
Copy link
Collaborator Author

keawade commented Dec 14, 2015

I like the second address idea.

@keawade
Copy link
Collaborator Author

keawade commented Dec 21, 2015

I'm going to close this issue and link it in the new issue I'm creating for this feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants