maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

[DOCS][skip ci] Adjusting production setup instructions as a result of Spaces/RBAC (#36890)

Browse source 
* Adjusting production setup instructions as a result of Spaces/RBAC

* Update docs/setup/production.asciidoc

Co-Authored-By: Larry Gregory <lgregorydev@gmail.com>
This commit is contained in:
Brandon Kobel 2019-05-22 10:44:36 -04:00 committed by GitHub
parent fac22a1149
commit b92c6d22ff
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/setup/production.asciidoc
View file

@ -26,16 +26,14 @@ You can use {stack-ov}/elasticsearch-security.html[{stack} {security-features}]
to control what {es} data users can access through Kibana.
When {security-features} are enabled, Kibana users have to log in. They need to
have the `kibana_user` role as well as access to the indices they
will be working with in Kibana.
have a role granting <<kibana-privileges, Kibana privileges>> as well as access
to the indices they will be working with in Kibana.
If a user loads a Kibana dashboard that accesses data in an index that they
are not authorized to view, they get an error that indicates the index does
not exist. The {security-features} do not currently provide a way to control
which users can load which dashboards.
not exist.
For information about setting up Kibana users, see
{kibana-ref}/using-kibana-with-security.html[Configuring security in Kibana].
For more information on granting access to Kibana, see <<xpack-security-authorization>>.
[float]
[[csp-strict-mode]]