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

feature request: password reset link in email rather than temp password #873

Open
stevenolen opened this issue Dec 1, 2015 · 0 comments
Labels

Comments

@stevenolen
Copy link
Member

A big user complaint is having to copy/paste the temp password that gets sent in order to log in again. It is a bit awkward and novice users have trouble with this action. It's a much more common procedure to send a one-time password reset link that, if clicked during the short window, will allow the user to set a new password. Current and proposed flows below:

Current flow:

  • user forgets password
  • user enters username and email and client sends request to user/reset_password
  • (assuming user exists) server generates password, marks account as new_account and sends password to user via email
  • user copies password from email and logs in with this user/pw combo
  • since new_account is set, user is forced to change password

Proposed flow:

  • user forgets password
  • user enters username and email and client sends request to user/reset_password
  • (assuming user exists) server generates a password reset code (which expires in 30 minutes) and sends link to user.
  • user clicks link in email and is directed to client to set a new password.
    • this should work similarly to the user/activate api -- the generated link allows the frontend to query an endpoint to see if the request was successful and if so, prompt user to set a new password.
  • Once reset the user will need to log in again, as the process wont contain the user's username

Thoughts?

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

No branches or pull requests

1 participant