Skip to content

Commit

Permalink
32 characters requirement for xpack.reporting.encryptionKey (elastic#…
Browse files Browse the repository at this point in the history
…72593) (elastic#73472)

Similar to https://www.elastic.co/guide/en/kibana/current/alert-action-settings-kb.html#general-alert-action-settings is a 32 character minimum length required for xpack.reporting.encryptionKey

Co-authored-by: Toby Sutor <55087308+toby-sutor@users.noreply.github.com>
  • Loading branch information
KOTungseth and toby-sutor authored Jul 28, 2020
1 parent a7f0c9d commit 2c8b5fd
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/settings/reporting-settings.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ You can configure `xpack.reporting` settings in your `kibana.yml` to:
| Set to `false` to disable the {report-features}.

| `xpack.reporting.encryptionKey`
| Set to any text string. By default, {kib} will generate a random key when it
| Set to an alphanumeric, at least 32 characters long text string. By default, {kib} will generate a random key when it
starts, which will cause pending reports to fail after restart. Configure this
setting to preserve the same key across multiple restarts and multiple instances of {kib}.

Expand Down

0 comments on commit 2c8b5fd

Please sign in to comment.