You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 17, 2019. It is now read-only.
I don't know exactly hos much was implemented the first time around, but I think there is a store method and an endpoint - but I believe it is incomplete.
The way it should work is:
Call GET /recovery/:email to ask for a recovery token.
The token is set on the user, and the e-mail is sent. At this point we want it to point at a passwordRecoveryUrl set as an ENV var. We want to suffix the token as ${passwordRecoveryUrl}/${token}.
Another endpoint, POST /recovery/:token, will take a { email: 'email', password: 'newPass' } body. If the token OR the e-mail does not match, it should return 404.
The text was updated successfully, but these errors were encountered:
I don't know exactly hos much was implemented the first time around, but I think there is a store method and an endpoint - but I believe it is incomplete.
The way it should work is:
GET /recovery/:email
to ask for a recovery token.passwordRecoveryUrl
set as anENV
var. We want to suffix the token as${passwordRecoveryUrl}/${token}
.POST /recovery/:token
, will take a{ email: 'email', password: 'newPass' }
body. If the token OR the e-mail does not match, it should return404
.The text was updated successfully, but these errors were encountered: