Skip to content

Conversation

@spinscale
Copy link
Contributor

This improves the error message when encrypting of sensitive watcher
data is configured, but no system file was specified in the keystore.
This error message is displayed on startup.

This also closes the input stream of the secure file properly.

Closes #43619

Message on start up is now

org.elasticsearch.bootstrap.StartupException: ElasticsearchException[setting [xpack.watcher.encryption_key] must be set in keystore]

reviewers note: Intend this to put into master and 7.x branches. please veto as part of your review.

This improves the error message when encrypting of sensitive watcher
data is configured, but no system file was specified in the keystore.
This error message is displayed on startup.

This also closes the input stream of the secure file properly.

Closes elastic#43619
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

@jakelandis jakelandis requested a review from jbaiera July 11, 2019 14:49
Copy link
Member

@jbaiera jbaiera left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jbaiera
Copy link
Member

jbaiera commented Jul 11, 2019

@elasticmachine update branch

@jbaiera
Copy link
Member

jbaiera commented Jul 12, 2019

@elasticmachine run elasticsearch-ci/2

@jbaiera
Copy link
Member

jbaiera commented Jul 12, 2019

@elasticmachine run elasticsearch-ci/packaging-sample

@jbaiera jbaiera merged commit 8020871 into elastic:master Jul 15, 2019
jbaiera pushed a commit to jbaiera/elasticsearch that referenced this pull request Jul 15, 2019
…3623)

This improves the error message when encrypting of sensitive watcher
data is configured, but no system file was specified in the keystore.
This error message is displayed on startup.

This also closes the input stream of the secure file properly.

Closes elastic#43619
jbaiera added a commit that referenced this pull request Jul 16, 2019
…44364)

This improves the error message when encrypting of sensitive watcher
data is configured, but no system file was specified in the keystore.
This error message is displayed on startup.

This also closes the input stream of the secure file properly.

Closes #43619
jbaiera added a commit that referenced this pull request Jul 16, 2019
…44365)

This improves the error message when encrypting of sensitive watcher
data is configured, but no system file was specified in the keystore.
This error message is displayed on startup.

This also closes the input stream of the secure file properly.

Closes #43619
@jpountz jpountz added v7.3.0 and removed v7.3.1 labels Jul 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Watcher: NPE when enabled but not configuring sensitive data encryption

5 participants