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] Password Recovery Flow #165

Closed
1 of 6 tasks
alexjball opened this issue Sep 28, 2021 · 1 comment
Closed
1 of 6 tasks

[FEATURE] Password Recovery Flow #165

alexjball opened this issue Sep 28, 2021 · 1 comment
Assignees
Labels
epic Large issues and features that involve multiple PR's or sub-issues

Comments

@alexjball
Copy link
Member

alexjball commented Sep 28, 2021

Figma

/v1/api/auth routes:

  • /resetPassword: POST with body {email: string, phoneNumber: string }. Support email before phone numbers. For security, returns 200 regardless of existing account.

Note: flask_user, the library we use to manage users, automatically installs routes related to password recovery and email verification. Rather than implement our own routes, we could leverage these. These are the /user routes listed by flask routes

Frontend Work

  • Build forgot password form
  • Connect form to /resetPassword endpoint
  • Test password recovery flow

Backend Work

  • Use flask_user to send and handle recovery emails
  • Configure credentials for sending emails
  • Create /resetPassword route
@alexjball alexjball added the epic Large issues and features that involve multiple PR's or sub-issues label Oct 14, 2021
@ryanmahan ryanmahan self-assigned this Nov 17, 2021
@ryanmahan
Copy link
Collaborator

ryanmahan commented Dec 1, 2021

Looks like a lot of the /user routes provided by flask-user are all packaged with the views provided (i.e. endpoints are locked behind views). Looking into seeing if we can change the email URL to direct to the frontend and use as much of the flask user routes as possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Large issues and features that involve multiple PR's or sub-issues
Projects
None yet
Development

No branches or pull requests

3 participants