Split AccountStorage and ForgotPasswordStorage (expiring now) #1150
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📁 Related issues
#744
✍️ Description
This PR will split the AccountStorage being used, into an AccountStorage (which still has the KeyValueStorage type) and a new ForgotPasswordStorage (of type ExpiringStorage).
The purpose of this change is to allow for ForgotPassword entries to be purged from the storage (be it in-memory or file based) when users don't click the link sent in the email. A default expiration of 15 minutes is added.
✅ PR check list
Before this pull request can be merged, a core maintainer will check whether