Refactor user email confirmation + password reset handling #919
No reviewers
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#919
Loading…
Reference in New Issue
No description provided.
Delete Branch "feature/email-confirmation"
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?
Description
This PR refactors the way user tokens (password request and email verification) and statuses are handled internally.
It introduces a new table
user_token
which stores all kinds of tokens and a bunch of helper methods to manage them. This could be expanded further in the future.It also removes the
IsActive
boolean field of a user to a more generalStatus
field to better distinguish if a user is disabled or only required to confirm their email address.Checklist