Skip to content
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

Set kibana reporting encryption key #2279

Closed
anyasabo opened this issue Dec 17, 2019 · 1 comment · Fixed by #3285
Closed

Set kibana reporting encryption key #2279

anyasabo opened this issue Dec 17, 2019 · 1 comment · Fixed by #3285
Assignees
Labels
>enhancement Enhancement of existing functionality

Comments

@anyasabo
Copy link
Contributor

Similar to the session encryption key, we should set the reporting key xpack.reporting.encryptionKey by default so that in progress reports can be resumed:

Set to any text string. By default, Kibana 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 Kibana.

I noticed this warning log message when verifying the other encryption key functionality:

{"type":"log","@timestamp":"2019-12-17T16:12:58Z","tags":["reporting","warning"],"pid":6,"message":"Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart, please set xpack.reporting.encryptionKey in kibana.yml"}

Docs:
https://www.elastic.co/guide/en/kibana/current/reporting-settings-kb.html#general-reporting-settings

@anyasabo anyasabo added the >enhancement Enhancement of existing functionality label Dec 17, 2019
@anyasabo
Copy link
Contributor Author

Ditto xpack.encrypted_saved_objects.encryptionKey

@anyasabo anyasabo self-assigned this Jan 8, 2020
@anyasabo anyasabo removed their assignment Mar 3, 2020
@anyasabo anyasabo self-assigned this Jun 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement Enhancement of existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant