honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Docs: Clarify sensitive fields watcher encryption (#31551) 

Clarify the scope of encrypting sensitive settings in watcher, which fields
are encrypted and if users can have their own encrypted fields.
This commit is contained in:
Alexander Reelsen 2018-06-26 16:24:28 +02:00 committed by GitHub
parent a72dc9e8fc
commit 8a6d062180
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
x-pack/docs/en/watcher/encrypting-data.asciidoc
View File

@ -6,6 +6,12 @@ information or details about your SMTP email service. You can encrypt this
data by generating a key and adding some secure settings on each node in your data by generating a key and adding some secure settings on each node in your
cluster. cluster.
Every `password` field that is used in your watch within a HTTP basic
authentication block - for example within a webhook, a HTTP input or when using
the reporting email attachment - will not be stored as plain text anymore. Also
be aware, that there is no way to configure your own fields in a watch to be
encrypted.
To encrypt sensitive data in {watcher}: To encrypt sensitive data in {watcher}:
. Use the {ref}/syskeygen.html[elasticsearch-syskeygen] command to create a system key file. . Use the {ref}/syskeygen.html[elasticsearch-syskeygen] command to create a system key file.