3.x: Security context not overridden #7512
Merged
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
Signed-off-by: David Kral <[email protected]>
oracle-contributor-agreement
bot
added
the
OCA Verified
Signed-off-by: David Kral <[email protected]>
tomas-langer
approved these changes
Sep 5, 2023
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.
Description
Security context is no longer overridden when combining WebSecurity and JAX-RS endpoint. This issue was happening in
SecurityPreMatchingFilterin cases whereWebSecurityauthenticated user.SecurityPreMatchingFilterobtained already processedSecurityContextand replaced it with not processed one.Fixes #7509
Backport of #7511
Documentation
None