We are using NiFi’s InvokeHTTP to POST files over HTTPS to MiNiFi IoT devices. MiNiFi is configured with JKS keystore/truststore files containing certificates signed by our CA and bound to the device hostnames. NiFi InvokeHTTP fails with a hostname verification error when connecting to the devices. We need to either disable the hostname the  Could you please advise the recommended   else how should configure invokehttp in nifi should we also add import certif minifi to nifi trustore please what it the logic to activate the https and send files to minifi ... View more

Hello Team, Currently we use NiFi’s InvokeHTTP to send files to a MiNiFi IoT device. The MiNiFi listenhttp is configured in the YAML and we are calling the device with: http + ip (device)+port Security requires we move this to HTTPS. On the NiFi side we configured SSLServiceContext and added a truststore. On the MiNiFi device we configured listenhttp in its YAML and provided a keystore and truststore (certificates are not machine-signed). After switching to HTTPS we see a hostname verification error  Question: is there a supported option in Cloudera / NiFi’s InvokeHTTP to use only a truststore and skip hostname verification? Alternatively, is there a recommended way to bypass or relax hostname verification on the MiNiFi side so the call succeeds?   Thanks ... View more