[Security] Fix impersonation being deauthenticated on every request#64213
Merged
Merged
[Security] Fix impersonation being deauthenticated on every request#64213
Conversation
|
I want this change rolled out urgently please |
This was referenced May 20, 2026
Merged
Merged
Merged
This file contains hidden or 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
3 participants
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.
In #64175 the
ROLE_PREVIOUS_ADMINrole-check block was reintroduced inContextListener::hasUserChanged()when merging from 6.4 up to 7.4. On 6.4 the matching half lives inSwitchUserListener, which appendsROLE_PREVIOUS_ADMINto the token's roles; on 7.4+ that code was removed back in 2023 (#50957), so the check now sees a role-count mismatch on every refresh and deauthenticates the impersonation token.This removes the stale half so the two halves stay consistent on 7.4+.