anchor.diff:  https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Managing_Smart_Cards/Configuring_a_Kerberos_5_Server.html[_https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Managing_Smart_Cards/Configuring_a_Kerberos_5_Server.html_]
   . This guide assumes that Kerberos already has been installed in the environment in which NiFi is running.
   
  -Note, the following procedures for kerberizing an Embedded Zookeeper server in your NiFI Node and kerberizing a zookeeper NiFI client will require that
  +Note, the following procedures for kerberizing an Embedded ZooKeeper server in your NiFi Node and kerberizing a ZooKeeper NiFi client will require that
   Kerberos client libraries be installed. This is accomplished in Fedora-based Linux distributions via:
   
   [source]
  
positive.code: This will cause the debug output to be written to the NiFi Bootstrap log file. By default, this is located at _$NIFI_HOME/logs/nifi-bootstrap.log_.
  This output can be rather verbose but provides extremely valuable information for troubleshooting Kerberos failures.
  
  
  
  [[bootstrap_properties]]
  Bootstrap Properties
  
negative.code: [template="glossary", id="terminology"]
  *Terminology* +
  
  *NiFi Cluster Coordinator*: A NiFi Cluster Cluster Coordinator is the node in a NiFi cluster that is responsible for carrying out
  tasks to manage which nodes are allowed in the cluster and providing the most up-to-date flow to newly joining nodes. When a
  DataFlow Manager manages a dataflow in a cluster, they are able to do so through the User Interface of any node in the cluster. Any
  change made is then replicated to all nodes in the cluster.
  