Docs: Clarify password protection support with keystore (#28157)

closes #27932
This commit is contained in:
Ryan Ernst 2018-01-09 15:01:37 -08:00 committed by GitHub
parent 5ac05faab5
commit 3fb0cb91a9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 2 deletions

View File

@ -3,8 +3,7 @@
Some settings are sensitive, and relying on filesystem permissions to protect Some settings are sensitive, and relying on filesystem permissions to protect
their values is not sufficient. For this use case, Elasticsearch provides a their values is not sufficient. For this use case, Elasticsearch provides a
keystore, which may be password protected, and the `elasticsearch-keystore` keystore and the `elasticsearch-keystore` tool to manage the settings in the keystore.
tool to manage the settings in the keystore.
NOTE: All commands here should be run as the user which will run Elasticsearch. NOTE: All commands here should be run as the user which will run Elasticsearch.
@ -14,6 +13,9 @@ documentation for each setting to see if it is supported as part of the keystore
NOTE: All the modifications to the keystore take affect only after restarting NOTE: All the modifications to the keystore take affect only after restarting
Elasticsearch. Elasticsearch.
NOTE: The elasticsearch keystore currently only provides obfuscation. In the future,
password protection will be added.
[float] [float]
[[creating-keystore]] [[creating-keystore]]
=== Creating the keystore === Creating the keystore