-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Remove auto_configure privilege for profiling #101026
Remove auto_configure privilege for profiling #101026
Conversation
With this commit we remove the `auto_configure` privilege for the Fleet service account that targets profiling-related indices. This privilege was needed to automatically create indices and data streams in the past but as this managed by the Elasticsearch plugin, there is no need to grant this privilege to Fleet-managed components.
Documentation preview: |
Pinging @elastic/es-security (Team:Security) |
Hi @danielmitterdorfer, I've created a changelog YAML for you. |
@elasticsearchmachine run elasticsearch-ci/bwc |
@elasticmachine merge upstream |
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.
LGTM
Thanks for retracting the privilege!
Have you thought about mixed versions scenarios, where an old component (fleet server maybe) might try to create the index the old way (not using the plugin) using the new credential from this PR?
Thanks for the feedback. We have changed the behavior with #96268, which is available since 8.9.0 and went GA in 8.10.0. Upgrades from the beta phase to a GA version are not supported (unless users delete all data and start from scratch) so that scenario should not affect us. |
With this commit we remove the
auto_configure
privilege for the Fleet service account that targets profiling-related indices. This privilege was needed to automatically create indices and data streams in the past but as this managed by the Elasticsearch plugin, there is no need to grant this privilege to Fleet-managed components.