[
https://issues.apache.org/jira/browse/NIFI-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150854#comment-15150854
]
ASF GitHub Bot commented on NIFI-1252:
--------------------------------------
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/229#issuecomment-185321319
@pvillard31 Thank you for contributing this fix against the last release.
This was handled via NIFI-1415 in commit
93e2c5219599f24b54517dd43195c3d121030c5e as part of the 0.5.0 release. I was
not able to reproduce and believe it should be have as desired. Please let us
know if this is not the case.
> The FetchSFTP processor has inconsistent behavior when using public/private
> keys for login
> ------------------------------------------------------------------------------------------
>
> Key: NIFI-1252
> URL: https://issues.apache.org/jira/browse/NIFI-1252
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: David A. Wynne
> Priority: Minor
>
> When using public/private keys for login in to a system with FetchSFTP, it
> requires the Private key passphrase to have a value. The other processors
> that have the capability to use public/private keys do not require that the
> same property have a value. The FetchSFTP processor should be modified to
> have the same behavior. I am testing in version NiFi-0.4.0-SNAPSHOT.
> If I put in a value for the property, it will work, it ignores the value
> since the key was created without a passphrase. So, it isn't a show stopper,
> just a little annoying.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
