fix(ras): destroy sessions on account verification #3328
Merged
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.
All Submissions:
Changes proposed in this Pull Request:
p1722617670146119-slack-C015W6BES8J
Replaces the strategy implemented in #1787.
Upon verification, we want to destroy existing sessions to prevent a bad actor having originated the account creation from accessing the, now verified, account. If the verification is for the current user, we destroy other sessions.
How to test the changes in this Pull Request:
\Newspack\Reader_Activation::set_reader_verified( $user_id );Other information: