Skip to content

Commit

Permalink
[DOCS][Reporting] Adds info about using a custom reporting index (ela…
Browse files Browse the repository at this point in the history
…stic#54052)

* [DOCS][Reporting] Adds info about using a custom reporting index

* [DOCS] Incorporates edits into reporting security doc
  • Loading branch information
gchaps committed Jan 7, 2020
1 parent 4f9bf11 commit 963480c
Showing 1 changed file with 24 additions and 0 deletions.
24 changes: 24 additions & 0 deletions docs/user/security/reporting.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,30 @@ that provides read and write privileges in
Go to *Management > Users*, add a new user, and assign the user the built-in
`reporting_user` role and your new custom role, `custom_reporting_user`.

[float]
==== With a custom index

If you are using Reporting with a custom index,
the `xpack.reporting.index` setting should begin
with `.reporting-*`. The default {kib} system user has
`all` privileges against the `.reporting-*` pattern of indices.

[source,js]
xpack.reporting.index: '.reporting-custom-index'

If you use a different pattern for the `xpack.reporting.index` setting,
you must create a custom role with appropriate access to the index, similar
to the following:

. Go to *Management > Roles*, and click *Create role*.
. Name the role `custom-reporting-user`.
. Specify the custom index and assign it the `all` index privilege.
. Go to *Management > Users* and create a new user with
the `kibana_system` role and the `custom-reporting-user` role.
. Configure {kib} to use the new account:
[source,js]
elasticsearch.username: 'custom_kibana_system'

[float]
[[reporting-roles-user-api]]
==== With the user API
Expand Down

0 comments on commit 963480c

Please sign in to comment.