How we can bypass the hostname validation in SSLCONTEXT SERVICES

nifirequest — Tue, 07 Oct 2025 15:14:02 GMT

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

Re: How we can bypass the hostname validation in SSLCONTEXT SERVICES

MattWho — Wed, 08 Oct 2025 17:39:42 GMT

@nifirequest

This appears to be a duplicate to the following community question:
https://community.cloudera.com/t5/Support-Questions/How-we-ignore-hostname-verification-certificate-for-minifi/td-p/412577

Did the response in that thread not help you?

Thank you,
Matt

question How we can bypass the hostname validation in SSLCONTEXT SERVICES in Support Questions

How we can bypass the hostname validation in SSLCONTEXT SERVICES

Re: How we can bypass the hostname validation in SSLCONTEXT SERVICES