Not sure I follow. We are talking about whitelisting configuration needed for NiFi and not Ambari.
The specific nifi.properties property that is used to add a whitelist of allowed http headers is found in the NiFi admin guide:
Hello @Matt Clarke,
It is ok.
"This Whitelist feature is already part of the HDF 3.1 release from Hortonworks and will be part of the Apache NiFi 1.6 release at a later time.
I thought that NIFI 1.5 (which is included in HDF 3.1) was not working and that HDF 3.1 provided throught ambari some Work around :)
Thanks for your help !
HDF is never running exactly the same version of Apache NiFi as you would find in the open community. Each HDF release is based off an Apache release version as the baseline with many bugs and/or enhancements added on top. So you may find apache bugs that are fixed in Apache NiFi 1.6 which are already fixed in the HDF 3.1 release.
If you can build NiFi, it is not so hard to back-port the whitelist feature to 1.5.0. You only need to cherry-pick two commits.
git clone -b rel/nifi-1.5.0 https://github.com/apache/nifi cd nifi # cherry-pick NIFI-4761 git cherry-pick 8cb09c301d6fef70cc8a02a4a7e80f3062ab58ae git cherry-pick e3c661daac69cdb2de43c3d66d9ed1ccc9c8dbc6 # If you need the tar ball mvn -T 2.0C clean install -DskipTests # If you need the RPM package mvn -T 2.0C clean install -DskipTests -Prpm
This works fine for us. Thanks.
Is there a way to turn off the Header Request checking entirely? This is causing hoopla with load balancers. SSL will take care of this on its own, yes?,
Is there a way to disable the Request Header check? This causes hellavu problems with load balancers.
There is no way to disable the strict hostname checking. The purpose is prevent NiFI from responding to requests that were directed at a different target host.
If the incoming request has hostname abc.example.com in the header, It is expected that the PrivateKeyEntry in the keystore being used by NiFi has that exact same hostname defined either as its CN or as a Subject Alternative Name (SAN).
NiFi does provide a mechanism to get around this hostname checking in Apache NIFi 1.6.0 or (HDF 3.1.x) versions.
This new property would get added to the nifi.properties file.
If you found this Answer addressed your original question, please take a moment to login and click "Accept" below the answer.
Thanks. What I have found is that incoming requests from the LB (aws NLB) were being rejected, even when the LB DNS was part of the SAN in the cert. Setting the nifi.web.proxy.host = <LB DNS>:9091 stopped this from happening, but now there is an error saying that the hostname should be <X>, where X is the private DNS name of the node. I will try adding the private DNS entries to the SAN to see if this resolves. Thanks.