anchor.diff:  
   Next, we need to tell NiFi to use this as our JAAS configuration. This is done by setting a JVM System Property, so we will edit the `conf/bootstrap.conf` file.
   If the Client has already been configured to use Kerberos, this is not necessary, as it was done above. Otherwise, we will add the following line to our _bootstrap.conf_ file:
  - 
  +
   [source]
   java.arg.15=-Djava.security.auth.login.config=./conf/zookeeper-jaas.conf
   
  
positive.code: 
  
  
  [[state_management]]
  State Management
  ----------------
  
negative.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.
  
  
  
  