You should not send the same token over and over, it's not even stored in the database for you to do that (what's stored is an encrypted version of it). Also when you request to reset a new password, the new token is generated and the user gets another X time to reset, so "within the expiry period" isn't something you should reuse either. Each new password request has its own period.
Is there anything preventing you from using it like that? Other than "requirements", are there any reason behind this need?
Carlos Antonio da Silva - via celular
--
---
You received this message because you are subscribed to the Google Groups "Devise" group.
To unsubscribe from this group and stop receiving emails from it, send an email to plataformatec-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to plataformatec-devise+unsub...@googlegroups.com.
I think it's not very common for users to ask for reset password many times, a normal user would do it once and go to their inbox. Only if they do not get the email in a timely fashion, they'd another I think.
For you to do that you'd have to save the raw token somehow, which is something devise does not do anymore for security reasons. You must take a look at devise recoverable model implementation, and override a couple methods there to achieve that.
Hope that helps.
Carlos Antonio da Silva - via celular
Thanks Carlos...
To unsubscribe from this group and stop receiving emails from it, send an email to plataformatec-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
---
You received this message because you are subscribed to the Google Groups "Devise" group.
To unsubscribe from this group and stop receiving emails from it, send an email to plataformatec-de...@googlegroups.com.