This repository has been archived by the owner on Jul 14, 2023. It is now read-only.
Session tokens #184
Open
Session tokens #184
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Pre-emptive step to disabling user accounts
Changes proposed in this pull request:
Have you made sure to add:
Screenshots and GIFs
Deploy notes
Need to run a DB migration upon deployment.
This PR is for adding the columns necessary for session tokens. It will create a session token for all new users moving forward. We will need to manually apply a DB migration that will create session tokens for all existing users and then change the user loader to use the session token.
Any Additional Information
Going forward, these migrations will be used to disable malicious users and implement security features to force the logout of a single user.