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
Description of the problem including expected versus actual behavior:
A user who requests a password reset is redirected to a check-email page that says the user has been sent an email containing a link that will expire in two hours.
If that link isn't used in two hours (or two days, or two months), the link redirects to to the resetting request page. But if the user submits the request again, the user is sent the same "expired" link.
Shouldn't a new confirmation token be generated when the existing one is more than retry_ttl old, or at least when it is more than token_ttl old?
It seems that ResettingController::sendEmailAction will use $user->getConfirmationToken() no matter how long ago the token was created.
The text was updated successfully, but these errors were encountered:
Symfony FOSUserBundle versions: v2.0.1
Description of the problem including expected versus actual behavior:
A user who requests a password reset is redirected to a check-email page that says the user has been sent an email containing a link that will expire in two hours.
If that link isn't used in two hours (or two days, or two months), the link redirects to to the resetting request page. But if the user submits the request again, the user is sent the same "expired" link.
Shouldn't a new confirmation token be generated when the existing one is more than retry_ttl old, or at least when it is more than token_ttl old?
It seems that ResettingController::sendEmailAction will use $user->getConfirmationToken() no matter how long ago the token was created.
The text was updated successfully, but these errors were encountered: