[
https://issues.apache.org/jira/browse/NIFI-4511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-4511.
------------------------------------
Fix Version/s: 1.5.0
Resolution: Fixed
> InvokeHTTP processor fails with TLS truststore config without keystore config
> -----------------------------------------------------------------------------
>
> Key: NIFI-4511
> URL: https://issues.apache.org/jira/browse/NIFI-4511
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Richard Midwinter
> Priority: Major
> Fix For: 1.5.0
>
> Attachments: trace.txt
>
>
> I think there's a new issue in the InvokeHTTP processor (probably introduced
> with the changes to move to OkHttp3) in 1.4.0.
> If you setup a TLS connection with a truststore but not a keystore the
> InvokeHTTP processors break with the stacktrace below. I'd suggest it perhaps
> shouldn't attempt to load the keystore if there isn't a path to one provided.
> A brief glance over the code suggests the issue would apply in reverse too
> (keystore provided, but not truststore), although that's perhaps a less
> common scenario.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
