Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[Security] Fix legacy impersonation system#46748
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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
When using the legacy authentication system with a user class notimplementing `EquatableInterface` (for instance, the default when usingSylius) a bug prevents the impersonation system to work properly.The switch is done correctly, but then the user is disconnected on thenext request because `SecurityContext::hasUserChanged()` compares theroles of the token in session with the roles of the temporary token, and theyaren't equal.`ROLE_PREVIOUS_ADMIN` is added in`SwitchUserListener::attemptSwitchUser()`, but then removed if thelegacy system is still enabled in `UserAuthenticationProvider`.It looks like this bug has been introduced while deprecating support forrole classes:symfony@d64372d#diff-914ec544d4f7b26fda540aea3d7bc57cc5057d76bfb9ad72047d77739e3bb5a3L115This patch fixes the issue (tested on a real Sylius project).
chalasr approved these changesJun 23, 2022
Member
chalasr left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
LGTM
stof approved these changesJun 23, 2022
fabpot approved these changesJun 23, 2022
Member
fabpot commentedJun 23, 2022
Thank you@dunglas. |
This was referencedJun 26, 2022
Merged
Merged
Merged
Sign up for freeto 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.
Uh oh!
There was an error while loading.Please reload this page.
When using the legacy authentication system with a user class not
implementing
EquatableInterface(for instance, the default when usingSylius) a bug prevents the impersonation system from working properly.
The switch is done correctly, but then the user is disconnected on the
next request because
SecurityContext::hasUserChanged()compares theroles of the token in session with the roles of the temporary token, and they
aren't equal.
ROLE_PREVIOUS_ADMINis added inSwitchUserListener::attemptSwitchUser(), but then removed if thelegacy system is still enabled in
UserAuthenticationProvider.It looks like this bug has been introduced while deprecating support for
role classes:d64372d#diff-914ec544d4f7b26fda540aea3d7bc57cc5057d76bfb9ad72047d77739e3bb5a3L115
This patch fixes the issue (tested on a real Sylius project).