Remember-Me Cookies #167
Labels
No labels
Bug
Cleanup/Refactor
Core Feature
Documentation
Feature
Performance Improvement
Security Improvement
UX/Accessibility
Unreproducable Bug
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Depends on
#169 Create Remember-Me Token Collection
rainbownapkin/canopy
#172 Split sessionUtils.js authenticateSessions()
rainbownapkin/canopy
#173 Create Remember-Me Middleware
rainbownapkin/canopy
#174 Kill Remember-Me Tokens with Sessions
rainbownapkin/canopy
#175 Add 'Stay Logged In' checkmark
rainbownapkin/canopy
Reference: rainbownapkin/canopy#167
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Create "Remember-Me" check mark next to login.
Remember-Me tokens should be based on public key authentication, with public keys stored in a dedicated Mongoose collection, looked up by UUID to prevent attackers from attempting to auth against a specific target, or identifying exact remember-me DB collection size.
Further Reading:
https://paragonie.com/blog/2015/04/secure-authentication-php-with-long-term-persistence#title.2.1
https://security.stackexchange.com/questions/44/how-to-securely-implement-a-remember-me-feature
https://developer.mozilla.org/en-US/docs/Web/API/Web_Authentication_API.
added #169 as child task
added #172 as child task
added #173 as child task
added #174 as child task
added #175 as child task
Started work on Remember Me Tokens:
895a8201a5Remember me tokens now nuked upon full account logout:
bc0657a702Cleaned up remember-me error handling:
d874f5e2daRemember Me Tokens Complete.