[VI-762] Fully destroying User redis on login so that specific fields don't persist between logins #19456
+9
−33
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.
Summary
User
redis when a user authenticates either through SSOe or SiSUser
model were persisting between logins in certain casesRelated issue(s)
Testing done
needs_accepted_terms_of_use
onUser
model fromfalse
totrue
and saved the recordneeds_accepted_terms_of_use
was properly set tofalse
What areas of the site does it impact?
Authentication
Acceptance criteria
needs_accepted_terms_of_use
orcredential_lock
field onUser
model that's created