fix: configure management security filter chain #18569
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
romansmirnov
force-pushed
the
rs-18568-management-security-filter-chain
branch
4 times, most recently
from
519bbde
to
8091609
Compare
romansmirnov
force-pushed
the
rs-18568-management-security-filter-chain
branch
from
8091609
to
22ad5ed
Compare
houssain-barouni
approved these changes
May 16, 2024
tmetzke
approved these changes
May 16, 2024
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
This PR ensures that all actuator endpoints are accessible and do not return the status code 401. The same applies to the
BrokerHealthRoutes(ready,startup, andhealth). Therefore, it defines a security filter chainmanagementSecurityonly applied when one of the definedrequestMatchersmatches. If none of therequestMatchersmatch, then the defaultrestGatewaySecuritysecurity filter chain is applied, requiring proper authentication.Related issues
closes #18568