apache/nifi repository overview

⁠Capabilities

This image currently supports running in standalone mode either unsecured or with user authentication provided through:

• Single User Authentication⁠
• Mutual TLS with Client Certificates⁠
• Lightweight Directory Access Protocol (LDAP)⁠

⁠Running a container

⁠Standalone Instance secured with HTTPS and Single User Authentication

The minimum to run a NiFi instance is as follows:

docker run --name nifi \
  -p 8443:8443 \
  -d \
  apache/nifi:latest

This will provide a running instance, exposing the instance UI to the host system on at port 8443, viewable at https://localhost:8443/nifi. The default configuration generates a random username and password on startup. NiFi writes the generated credentials to the application log.

The following command can be used to find the generated credentials on operating systems with grep installed:

docker logs nifi | grep Generated

NiFi logs the generated credentials as follows:

Generated Username [USERNAME]
Generated Password [PASSWORD]

Environment variables can be used to set the NiFi communication ports and hostname using the Docker '-e' switch as follows:

docker run --name nifi \
  -p 9443:9443 \
  -d \
  -e NIFI_WEB_HTTPS_PORT='9443' \
  apache/nifi:latest

Single User Authentication credentials can be specified using environment variables as follows:

docker run --name nifi \
  -p 8443:8443 \
  -d \
  -e SINGLE_USER_CREDENTIALS_USERNAME=admin \
  -e SINGLE_USER_CREDENTIALS_PASSWORD=ctsBtRBKHRAx69EqUghvvgEvjnaLjFEB \
  apache/nifi:latest

Please note that the password must be 12 characters minimum, otherwise NiFi will generate a random username and password. See secure.sh and start.sh scripts for supported environment variables.

⁠Standalone Instance secured with HTTPS and Mutual TLS Authentication

In this configuration, the user will need to provide certificates and associated configuration information. Of particular note, is the AUTH environment variable which is set to tls. Additionally, the user must provide an the DN as provided by an accessing client certificate in the INITIAL_ADMIN_IDENTITY environment variable. This value will be used to seed the instance with an initial user with administrative privileges. Finally, this command makes use of a volume to provide certificates on the host system to the container instance.

docker run --name nifi \
  -v /User/dreynolds/certs/localhost:/opt/certs \
  -p 8443:8443 \
  -e AUTH=tls \
  -e KEYSTORE_PATH=/opt/certs/keystore.jks \
  -e KEYSTORE_TYPE=JKS \
  -e KEYSTORE_PASSWORD=QKZv1hSWAFQYZ+WU1jjF5ank+l4igeOfQRp+OSbkkrs \
  -e TRUSTSTORE_PATH=/opt/certs/truststore.jks \
  -e TRUSTSTORE_PASSWORD=rHkWR1gDNW3R9hgbeRsT3OM3Ue0zwGtQqcFKJD2EXWE \
  -e TRUSTSTORE_TYPE=JKS \
  -e INITIAL_ADMIN_IDENTITY='CN=Random User, O=Apache, OU=NiFi, C=US' \
  -d \
  apache/nifi:latest

⁠Standalone Instance secured with HTTPS and LDAP Authentication

In this configuration, the user will need to provide certificates and associated configuration information. Optionally, if the LDAP provider of interest is operating in LDAPS or START_TLS modes, certificates will additionally be needed. Of particular note, is the AUTH environment variable which is set to ldap. Additionally, the user must provide a DN as provided by the configured LDAP server in the INITIAL_ADMIN_IDENTITY environment variable. This value will be used to seed the instance with an initial user with administrative privileges. Finally, this command makes use of a volume to provide certificates on the host system to the container instance.

⁠For a minimal, connection to an LDAP server using SIMPLE authentication:

docker run --name nifi \
  -v /User/dreynolds/certs/localhost:/opt/certs \
  -p 8443:8443 \
  -e AUTH=ldap \
  -e KEYSTORE_PATH=/opt/certs/keystore.jks \
  -e KEYSTORE_TYPE=JKS \
  -e KEYSTORE_PASSWORD=QKZv1hSWAFQYZ+WU1jjF5ank+l4igeOfQRp+OSbkkrs \
  -e TRUSTSTORE_PATH=/opt/certs/truststore.jks \
  -e TRUSTSTORE_PASSWORD=rHkWR1gDNW3R9hgbeRsT3OM3Ue0zwGtQqcFKJD2EXWE \
  -e TRUSTSTORE_TYPE=JKS \
  -e INITIAL_ADMIN_IDENTITY='cn=admin,dc=example,dc=org' \
  -e LDAP_AUTHENTICATION_STRATEGY='SIMPLE' \
  -e LDAP_MANAGER_DN='cn=admin,dc=example,dc=org' \
  -e LDAP_MANAGER_PASSWORD='password' \
  -e LDAP_USER_SEARCH_BASE='dc=example,dc=org' \
  -e LDAP_USER_SEARCH_FILTER='cn={0}' \
  -e LDAP_IDENTITY_STRATEGY='USE_DN' \
  -e LDAP_URL='ldap://ldap:389' \
  -d \
  apache/nifi:latest

⁠The following, optional environment variables may be added to the above command when connecting to a secure LDAP server configured with START_TLS or LDAPS

-e LDAP_TLS_KEYSTORE: ''
-e LDAP_TLS_KEYSTORE_PASSWORD: ''
-e LDAP_TLS_KEYSTORE_TYPE: ''
-e LDAP_TLS_TRUSTSTORE: ''
-e LDAP_TLS_TRUSTSTORE_PASSWORD: ''
-e LDAP_TLS_TRUSTSTORE_TYPE: ''

⁠Clustering can be enabled by using the following properties to Docker environment variable mappings.

⁠nifi.properties

⁠state-management.xml

⁠Using the Toolkit

Start the container:

docker run -d --name nifi apache/nifi

After NiFi has been started, it is possible to run toolkit commands against the running instance:

docker exec -ti nifi nifi-toolkit-current/bin/cli.sh nifi current-user
anonymous

⁠Configuration Information

The following ports are specified by default in Docker for NiFi operation within the container and can be published to the host.

The Variable Registry can be configured for the docker image using the NIFI_VARIABLE_REGISTRY_PROPERTIES environment variable.

The JVM Memory initial and maximum heap size can be set using the NIFI_JVM_HEAP_INIT and NIFI_JVM_HEAP_MAX environment variables. These use values acceptable to the JVM Xmx and Xms parameters such as 1g or 512m.

The JVM Debugger can be enabled by setting the environment variable NIFI_JVM_DEBUGGER to any value.

NOTE: If NiFi is proxied at context paths other than the root path of the proxy, the paths need to be set in the nifi.web.proxy.context.path property, which can be assigned via the environment variable NIFI_WEB_PROXY_CONTEXT_PATH.

NOTE: If mapping the HTTPS port specifying trusted hosts should be provided for the property nifi.web.proxy.host. This property can be specified to running instances via specifying an environment variable at container instantiation of NIFI_WEB_PROXY_HOST.