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

[DOCS] Correct keystore commands for Email and Jira actions in Watcher (#40417) (#40612)

This commit is contained in:
James Rodewig 2019-04-01 08:25:26 -04:00 committed by GitHub
parent 287e334ef3
commit 39756fa538
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 10 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
x-pack/docs/en/watcher/actions/email.asciidoc
View File

@ -325,7 +325,7 @@ In order to store the account SMTP password, use the keystore command
[source,yaml]
--------------------------------------------------
bin/elasticsearch-keystore xpack.notification.email.account.gmail_account.smtp.secure_password
bin/elasticsearch-keystore add xpack.notification.email.account.gmail_account.smtp.secure_password
--------------------------------------------------
If you get an authentication error that indicates that you need to continue the
@ -363,7 +363,7 @@ In order to store the account SMTP password, use the keystore command
[source,yaml]
--------------------------------------------------
bin/elasticsearch-keystore xpack.notification.email.account.outlook_account.smtp.secure_password
bin/elasticsearch-keystore add xpack.notification.email.account.outlook_account.smtp.secure_password
--------------------------------------------------
@ -400,7 +400,7 @@ In order to store the account SMTP password, use the keystore command
[source,yaml]
--------------------------------------------------
bin/elasticsearch-keystore xpack.notification.email.account.ses_account.smtp.secure_password
bin/elasticsearch-keystore add xpack.notification.email.account.ses_account.smtp.secure_password
--------------------------------------------------
NOTE: You need to use your Amazon SES SMTP credentials to send email through

11
x-pack/docs/en/watcher/actions/jira.asciidoc
View File

@ -109,12 +109,15 @@ Jira account you need to specify (see {ref}/secure-settings.html[secure settings
[source,yaml]
--------------------------------------------------
bin/elasticsearch-keystore xpack.notification.jira.account.monitoring.secure_url
bin/elasticsearch-keystore xpack.notification.jira.account.monitoring.secure_user
bin/elasticsearch-keystore xpack.notification.jira.account.monitoring.secure_password
bin/elasticsearch-keystore add xpack.notification.jira.account.monitoring.secure_url
bin/elasticsearch-keystore add xpack.notification.jira.account.monitoring.secure_user
bin/elasticsearch-keystore add xpack.notification.jira.account.monitoring.secure_password
--------------------------------------------------
deprecated[The insecure way of storing sensitive data (`url`, `user` and `password`) in the configuration file or the cluster settings is deprecated]
[WARNING]
======
Storing sensitive data (`url`, `user` and `password`) in the configuration file or the cluster settings is insecure and has been deprecated. Please use {es}'s secure {ref}/secure-settings.html[keystore] method instead.
======
To avoid credentials that transit in clear text over the network, {watcher} will
reject `url` settings like `http://internal-jira.elastic.co` that are based on