Omit token field from new auth token db entries #541
Merged
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.
Only store token hash for newly created API tokens. Phase 3 of #343
Anywhere we query the AuthToken DB for
"token = ?", tokenhas already been replaced with"token = ? or token_hash = ?", token, GetTokenHash(token), so this does not effect the validity of any tokens, existing or new.Demoing creating a token, using it to re-authenticate, revoke another token, and create yet another token.
Screen.Recording.2022-11-17.at.6.48.12.PM.mov
This is the state of the DB after this flow:
