From da3d9dcf698313e49b1afd251d65c36a1d05016d Mon Sep 17 00:00:00 2001 From: Lisa Cawley Date: Wed, 1 Nov 2017 09:21:11 -0700 Subject: [PATCH] [DOCS] Added hide_settings to security settings (elastic/x-pack-elasticsearch#2801) * [DOCS] Added hide_settings to security settings * [DOCS] Addressed feedback about hide_settings Original commit: elastic/x-pack-elasticsearch@6a6d394c71578bd851e7d49a6344f7a27794ac41 --- docs/en/settings/security-settings.asciidoc | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/docs/en/settings/security-settings.asciidoc b/docs/en/settings/security-settings.asciidoc index 53581a74905..1ffbb51961c 100644 --- a/docs/en/settings/security-settings.asciidoc +++ b/docs/en/settings/security-settings.asciidoc @@ -8,9 +8,9 @@ You configure `xpack.security` settings to <> and perform message authentication, -<>, <>, -and <>. +<>, +<>, and +<>. All of these settings can be added to the `elasticsearch.yml` configuration file, with the exception of the secure settings, which you add to the {es} keystore. @@ -29,6 +29,13 @@ need to disable {security} in those `kibana.yml` files. For more information about disabling {security} in specific {kib} instances, see {kibana-ref}/security-settings-kb.html[{kib} Security Settings]. +`xpack.security.hide_settings`:: +A comma-separated list of settings that are omitted from the results of the +<>. You can use wildcards to include +multiple settings in the list. For example, the following value hides all the +settings for the ad1 realm: `xpack.security.authc.realms.ad1.*`. The API already +omits all `ssl` settings, `bind_dn`, and `bind_password` due to the +sensitive nature of the information. [float] [[password-security-settings]]