This is an automated email from the ASF dual-hosted git repository.
pvillard pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/nifi.git
The following commit(s) were added to refs/heads/master by this push:
new 7f49c6b NIFI-6907 Added nifi.bootstrap.sensitive.key to Bootstrap
Properties section in Admin Guide
7f49c6b is described below
commit 7f49c6b76aa930e8c00d5e3d11dd6d947cc31a3e
Author: Andrew Lim <[email protected]>
AuthorDate: Wed Dec 11 16:47:37 2019 -0500
NIFI-6907 Added nifi.bootstrap.sensitive.key to Bootstrap Properties
section in Admin Guide
Signed-off-by: Pierre Villard <[email protected]>
This closes #3927.
---
nifi-docs/src/main/asciidoc/administration-guide.adoc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/nifi-docs/src/main/asciidoc/administration-guide.adoc
b/nifi-docs/src/main/asciidoc/administration-guide.adoc
index 07b0a46..fc07438 100644
--- a/nifi-docs/src/main/asciidoc/administration-guide.adoc
+++ b/nifi-docs/src/main/asciidoc/administration-guide.adoc
@@ -2147,6 +2147,9 @@ take effect only after NiFi has been stopped and
restarted.
|`java.arg.N`|Any number of JVM arguments can be passed to the NiFi JVM when
the process is started. These arguments are defined by adding properties to
_bootstrap.conf_ that
begin with `java.arg.`. The rest of the property name is not
relevant, other than to differentiate property names, and will be ignored. The
default includes
properties for minimum and maximum Java Heap size, the garbage
collector to use, etc.
+|`nifi.bootstrap.sensitive.key`|The master key in hexadecimal format for
encrypted sensitive configuration values. When NiFi is started, the master key
is used to decrypt sensitive values from the _nifi.properties_ file into memory
for later use.
+
+The Encrypt-Config Tool can be used to specify the master key, encrypt
sensitive values in _nifi.properties_ and update _bootstrap.conf_. See the
<<toolkit-guide.adoc#encrypt_config_tool,NiFi Toolkit Guide>> for an example.
|`notification.services.file`|When NiFi is started, or stopped, or when the
Bootstrap detects that NiFi has died, the Bootstrap is able to send
notifications of these events
to interested parties. This is configured by
specifying an XML file that defines which notification services can be used.
More about this
file can be found in the <<notification_services>>
section.
