fix(auth): store reset token expiry in SQLite datetime format - #58
Merged
Conversation
toISOString() produces 'YYYY-MM-DDTHH:MM:SS.mmmZ' but SQLite's
datetime('now') returns 'YYYY-MM-DD HH:MM:SS'. The lexical comparison
in accountForResetToken always evaluates incorrectly because 'T' (0x54)
sorts after space (0x20), so tokens appear valid for up to ~24h instead
of the intended 1 hour.
Store in SQLite's native format so the comparison is correct.
Fixes moshcoder#44
This file contains hidden or 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
2 participants
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.
toISOString() produces YYYY-MM-DDTHH:MM:SS.mmmZ but SQLite datetime(now) returns YYYY-MM-DD HH:MM:SS. The T (0x54) always sorts after space (0x20), so the lexical comparison in accountForResetToken makes tokens appear valid for up to ~24h instead of the intended 1 hour.
Store in SQLite native format so the comparison is correct.
Fixes #44