-
Couldn't load subscription status.
- Fork 25.6k
Update kibana_system privileges with access to .apm-source-map
#92160
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
Conversation
|
@sqren please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
|
Pinging @elastic/es-security (Team:Security) |
|
@tvernum apply spotless (pretty please) |
Thanks for the ping! The change looks good from the Kibana perspective. |
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
In elastic/kibana#146367 Kibana will create a system index
.apm-source-mapat startup. All access to the index (creation, indexing, reading) will happen through the system user (kibana_system).kibana_systemalready has access to.apm-agent-configurationand.apm-custom-link. Following this pattern the role should also be granted access to.apm-source-map.