[
https://issues.apache.org/jira/browse/NIFI-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15150847#comment-15150847
]
Aldrin Piri edited comment on NIFI-1252 at 2/17/16 5:41 PM:
------------------------------------------------------------
This was resolved by removing the custom validation in NIFI-1415
was (Author: aldrin):
This was resolved by removing the custom validation.
> 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)
