Use same system index pattern in restricted names #84180
Merged
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
The index pattern that was used for the ".security" system index was not identical to the pattern used in RestrictedIndices. The consequence was that it would be possible for a user without restricted indices access to create an index that would get caught by the system indices pattern, which could lead to confusion. In 8.0 all system indices are automatically restricted, using the index name pattern from the system index descriptor, so in 7.17 we are changing the restricted index name to cover the same set of names as the system index descriptor
tvernum
added
>enhancement
:Security/Authorization
Collaborator
|
Pinging @elastic/es-security (Team:Security) |
Collaborator
|
Hi @tvernum, I've created a changelog YAML for you. |
tvernum
added
the
auto-merge-without-approval
Contributor
Author
|
@elasticmachine run elasticsearch-ci/packaging-tests-unix-sample please
|
tvernum
removed
the
auto-merge-without-approval
Contributor
Author
|
@elasticmachine run elasticsearch-ci/packaging-tests-unix-sample please |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
The index pattern that was used for the ".security" system index was
not identical to the pattern used in RestrictedIndices. The
consequence was that it would be possible for a user without
restricted indices access to create an index that would get caught by
the system indices pattern, which could lead to confusion.
In 8.0 all system indices are automatically restricted, using the
index name pattern from the system index descriptor, so in 7.17 we are
changing the restricted index name to cover the same set of names as
the system index descriptor