Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 2 commits into from
Mar 28, 2019
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b97fdac
Correct keystore commands for Email and Jira actions for Watcher
jrodewig Mar 25, 2019
f5e8bb6
Update depcrecation note to recommend keystore for secure creds
jrodewig Mar 25, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions x-pack/docs/en/watcher/actions/email.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
--------------------------------------------------


Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -443,7 +443,7 @@ In order to store the account SMTP password, use the keystore command

[source,yaml]
--------------------------------------------------
bin/elasticsearch-keystore xpack.notification.email.account.exchange_account.smtp.secure_password
bin/elasticsearch-keystore add xpack.notification.email.account.exchange_account.smtp.secure_password
--------------------------------------------------

[float]
Expand Down
11 changes: 7 additions & 4 deletions x-pack/docs/en/watcher/actions/jira.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down