github-mirrors/logstash
1
0
Fork 0
mirror of https://github.com/elastic/logstash.git synced 2025-04-24 14:47:19 -04:00
Code Issues Projects Releases Packages Wiki Activity

[doc] missing role for config management integration (#10341) (#11856)

Browse source 
logstash_admin role is not enough.
As the ls-security page mentions correctly:
"The user you specify here must have the built-in logstash_admin role as well as the logstash_writer role that you created earlier"

Updates static settings for extra role needed

Co-authored-by: Karen Metts <35154725+karenzone@users.noreply.github.com>

Co-authored-by: Edu González de la Herrán <25320357+eedugon@users.noreply.github.com>
This commit is contained in:
Karen Metts 2020-04-30 14:28:30 -04:00 • committed by GitHub
parent 8f142fc8bc
commit 4b8797bd9f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/static/management/configuring-centralized-pipelines.asciidoc vendored
View file

@ -31,8 +31,8 @@ centrally manage.
. Restart Logstash.
. If your Elasticsearch cluster is protected with basic authentication, assign
the `logstash_admin` role to any users who will use centralized pipeline
management. See <<ls-security>>.
the built-in `logstash_admin` role as well as the `logstash_writer` role to any users who will use centralized pipeline
management. See <<ls-security>> for more information.
NOTE: Centralized management is disabled until you configure and enable
{security-features}.

6
docs/static/settings/configuration-management-settings.asciidoc vendored
View file

@ -52,9 +52,9 @@ section in your Logstash configuration, or a different one. Defaults to
If your {es} cluster is protected with basic authentication, these settings
provide the username and password that the Logstash instance uses to
authenticate for accessing the configuration data.
The username you specify here should have the `logstash_admin` role, which
provides access to `.logstash-*` indices for managing configurations.
authenticate for accessing the configuration data. The username you specify here
should have the built-in `logstash_admin` role and the customized `logstash_writer` role, which provides access to `.logstash-*`
indices for managing configurations.
`xpack.management.elasticsearch.proxy`::