[NIFI-1252] The FetchSFTP processor has inconsistent behavior when using public/private keys for login

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Assignee: Unassigned
• Reporter: Wynner
• Created: 04/Dec/15 18:33
• Updated: 17/Feb/16 21:13
• Resolved: 17/Feb/16 20:57

Description

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.

Issue Links

• duplicates: NIFI-1415 FetchSFTP should not require password or private key passphrase
• relates to: NIFI-1525 Audit use of private keys throughout application