Fix EZP-23971: If a user is removed while logged in, session for that user will throw an exception #12
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
… user will throw an exception > https://jira.ez.no/browse/EZP-23971 When in legacy mode, authentication is completely delegated to the legacy kernel. However currently logged in user is also injected in the Repository to make it usable with appropriate permissions. Problem is that when the user is removed while a session for this user is still open, Symfony stack still tries to inject it in the repository, failing with a nasty exception. This PR fixes the issue.
|
+1 |
|
+1 (Seems to me I wasn't all that far off, but devils, details, etc.) |
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.
Relates to ezsystems/ezpublish-kernel#1188
When in legacy mode, authentication is completely delegated to the legacy kernel. However currently logged in user is also injected in the Repository to make it usable with appropriate permissions.
Problem is that when the user is removed while a session for this user is still open, Symfony stack still tries to inject it in the repository, failing with a nasty exception.
This PR fixes the issue.