NIFI-2664 Moving System.setProperty for krb5.conf to NiFi startup, an… #946
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…d removing conflicting property from KerberosProvider config
Rather than add code to all of the Kafka processors to set the system property, it makes more sense for NiFi to set it once during start up. Then it will be available to HDFS, HBase, and Kafka processors, as well as the Kerberos login provider.
We also had a potentially conflicting property in the login provider, where you could set the krb5.conf file there which would eventually set the system property and potentially overwrite the one that could have been set from nifi.properties. Now there is on the value in nifi.properties.