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
In the Mongo package, we could store the reset password tokens in a separate collection and use the TTL feature of Mongo to delete them automatically once they expire.
Right now if I ask a lot of reset password emails but actually never use them, the user object will never be cleaned and the service.password.reset object will be set to an array containing all the tokens. The tokens are only cleared if a user finish the process currently.
Additional context
This is a breaking change on the database schema.
Also, the same thing can be applied to:
verify email tokens
sessions
The text was updated successfully, but these errors were encountered:
@sakulstra the sessions are stored as a token saved inside the user object and TTL is not working in such case. If they wanted to use it they would have to move the sessions to a separate collection.
I remember reading an issue about this but they said that since it was not causing performance issues there was no point to move it to a separate collection.
Feature request
In the Mongo package, we could store the reset password tokens in a separate collection and use the TTL feature of Mongo to delete them automatically once they expire.
Right now if I ask a lot of reset password emails but actually never use them, the user object will never be cleaned and the
service.password.reset
object will be set to an array containing all the tokens. The tokens are only cleared if a user finish the process currently.Additional context
This is a breaking change on the database schema.
Also, the same thing can be applied to:
The text was updated successfully, but these errors were encountered: