-
Notifications
You must be signed in to change notification settings - Fork 25.3k
Remove implicit index monitor privilege #37774
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
albertzaharovits
merged 15 commits into
elastic:master
from
albertzaharovits:remove_implicit_monitor_privilege
Jan 29, 2019
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
15329d0
W00p w00p
albertzaharovits bca3eec
Test monitoring on restricted indices for monitoring collector
albertzaharovits 6e77830
breaking change note
albertzaharovits dc414fa
Merge branch 'master' into remove_implicit_monitor_privilege
albertzaharovits dc9675b
SecuritySettingsSource test_user allow_restricted_indices
albertzaharovits 973c0dc
Merge branch 'master' into remove_implicit_monitor_privilege
albertzaharovits 494db49
Merge branch 'master' into remove_implicit_monitor_privilege
albertzaharovits 4099d68
Integ test for index monitoring on wildcards
albertzaharovits 5545c7b
Merge branch 'master' into remove_implicit_monitor_privilege
albertzaharovits d360041
assertSecurityIndexActive()
albertzaharovits 18e7627
Merge branch 'master' into remove_implicit_monitor_privilege
albertzaharovits 06e0e32
test _cat/indices with wildcards
albertzaharovits dd9ff67
Merge branch 'master' into remove_implicit_monitor_privilege
albertzaharovits e2c30e9
Remove mock HTTP
albertzaharovits 3fe97af
Merge branch 'master' into remove_implicit_monitor_privilege
albertzaharovits File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to make sure the internal security indices are created here. Maybe we create a user and a role and validate that the security indices exist
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll also want to look at testing the cluster health api at the indices and shards levels. Same for the cluster stats api
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cluster Health and Stats are authorized as cluster actions
cluster:monitor/*
and will see all indices irrespective of the change proposed here.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I went back into the time machine and figured out the API that this leniency for monitoring came from. It is the _cat/indices API. I am pretty sure it will still fail based on the way it works so I think we should:
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We dug into this over slack.
Jay pointed me to the commit that added this leniency and we identified that it was no longer relevant as the cause got inadvertently removed by #18545 .
As discussed, I have added a test for
_cat/indices/*
to validate that no unauthorized exception is thrown (when the wildcard includes the unauthorized.security
index).