Update security to gracefully handle an invalid cluster alias #138546
+70
−1
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
Collaborator
|
Pinging @elastic/es-security (Team:Security) |
slobodanadamovic
approved these changes
Nov 28, 2025
Contributor
slobodanadamovic
left a comment
There was a problem hiding this comment.
LGTM 👍
As discussed internally, let's also adjust the now failing AuthorizationServiceTests.testUserWithNoRolesCannotPerformLocalSearch test.
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.
Updates the security framework to return a 404 when an invalid cluster alias is provided in a request. Previously, when security was enabled, a 403 was returned even when the user had (theoretical) access to the missing cluster.