Replace superuser role for API keys (#81977)#82650
Merged
ywangd merged 5 commits intoelastic:8.0from Jan 17, 2022
Merged
Conversation
This PR replace superuser role of an API key with the new limited superuser role to prevent write access to system indices. The replacement should only happen to the builtin superuser role. If there is a user-created role that has the exact same definition as the superuser role, it will not be replaced because we consider users are explicitly opt-in for ALL access in this scenario. Relates: elastic#81400
Collaborator
|
Pinging @elastic/es-security (Team:Security) |
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
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.
This PR replace superuser role of an API key with the new limited
superuser role to prevent write access to system indices.
The replacement should only happen to the builtin superuser role.
If there is a user-created role that has the exact same definition as
the superuser role, it will not be replaced because we consider users
are explicitly opt-in for ALL access in this scenario.
Relates: #81400