Skip to content

Commit 8a6d062

Browse files
authored
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.
1 parent a72dc9e commit 8a6d062

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

x-pack/docs/en/watcher/encrypting-data.asciidoc

+6
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,12 @@ information or details about your SMTP email service. You can encrypt this
66
data by generating a key and adding some secure settings on each node in your
77
cluster.
88

9+
Every `password` field that is used in your watch within a HTTP basic
10+
authentication block - for example within a webhook, a HTTP input or when using
11+
the reporting email attachment - will not be stored as plain text anymore. Also
12+
be aware, that there is no way to configure your own fields in a watch to be
13+
encrypted.
14+
915
To encrypt sensitive data in {watcher}:
1016

1117
. Use the {ref}/syskeygen.html[elasticsearch-syskeygen] command to create a system key file.

0 commit comments

Comments
 (0)