HTTPS doesn’t work without a certificate. It’s just not possible. What is possible is for a non-secured webservice to listen on port 443 in which case you can use an http://<url>:443 style invocation. However, the most likely scenario is that you are using a self-signed certificate, in which case you’ll have to add the certificates to the truststore. See http://apache-nifi-developer-list.39713.n7.nabble.com/How-to-trust-another-certificate-from-within-nifi-flows-td17950.html for details.
Martijn On Mon, 10 Jun 2019, at 08:35, Tomislav Novosel wrote: > Yeah, I was thinking about that. But what if service doesn't have any > certificates at alL? > I think that service listens on K8S cluster without SSL certs and inside our > corporate network. > > BR, > Tom > > On Mon, 3 Jun 2019 at 16:16, Bryan Bende <[email protected]> wrote: >> Hello, >> >> You should be specifying an SSL Context Service in the processor which >> points to a truststore that trusts the certificate of the service you >> are calling. >> >> Alternatively, if the CA certs system truststore trusts the service >> cert then it should also work. >> >> Thanks, >> >> Bryan >> >> On Mon, Jun 3, 2019 at 10:14 AM Tomislav Novosel <[email protected]> >> wrote: >> > >> > Hi all, >> > >> > I have a case where I need to send POST request on one enpoint which is >> located >> > on K8S cluster and behind reverse proxy. Only HTTPS can be used. >> > If I put value of endpoint using https:// I get error 'Unable to find >> valid certification path to requested target'. >> > I spoke to my admin/devops guy and he says there is no other way to >> access that endpoint other than URL he gave me. >> > >> > Is there a way to bypass SSL verification or something else? >> > >> > Thanks, >> > BR, >> > Tom
