honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-03-24 17:09:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

[DOCS] Removed obsolete warning about no way to securely store passwords (#55133) (#55140)

Browse Source 
* [DOCS] Removed obsolete warning about no way to securely store passwords.

* Update x-pack/docs/en/watcher/actions/email.asciidoc

Co-Authored-By: James Rodewig <james.rodewig@elastic.co>
This commit is contained in:
debadair 2020-04-13 21:38:32 -07:00 committed by GitHub
parent 52bebec51f
commit e8fa539bea
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -252,17 +252,14 @@ messages can contain basic HTML tags. You can control which groups of tags are
allowed by <<email-html-sanitization, Configuring HTML Sanitization Options>>.
You configure the accounts {watcher} can use to send email in the
`xpack.notification.email` namespace in `elasticsearch.yml`.
`xpack.notification.email` namespace in `elasticsearch.yml`.
The password for the specified SMTP user is stored securely in the
<<secure-settings, {es} keystore>>.
If your email account is configured to require two step verification, you need
to generate and use a unique App Password to send email from {watcher}.
Authentication will fail if you use your primary password.
IMPORTANT: Currently, neither Watcher nor Shield provide a mechanism to encrypt
settings in `elasticsearch.yml`. Because the email account credentials appear
in plain text, you should limit access to `elasticsearch.yml` to the user that
you use to run Elasticsearch.
[[email-profile]]
{watcher} provides three email profiles that control how MIME messages are
structured: `standard` (default), `gmail`, and `outlook`. These profiles
@ -314,7 +311,7 @@ xpack.notification.email.account:
user: <username>
--------------------------------------------------
In order to store the account SMTP password, use the keystore command
To store the account SMTP password, use the keystore command
(see {ref}/secure-settings.html[secure settings])
[source,yaml]
@ -352,7 +349,7 @@ xpack.notification.email.account:
user: <email.address>
--------------------------------------------------
In order to store the account SMTP password, use the keystore command
To store the account SMTP password, use the keystore command
(see {ref}/secure-settings.html[secure settings])
[source,yaml]
@ -389,7 +386,7 @@ xpack.notification.email.account:
--------------------------------------------------
<1> `smtp.host` varies depending on the region
In order to store the account SMTP password, use the keystore command
To store the account SMTP password, use the keystore command
(see {ref}/secure-settings.html[secure settings])
[source,yaml]
@ -432,7 +429,7 @@ xpack.notification.email.account:
it is a good idea to check with your system administrator if you receive
authentication-related failures.
In order to store the account SMTP password, use the keystore command
To store the account SMTP password, use the keystore command
(see {ref}/secure-settings.html[secure settings])
[source,yaml]