You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by GitBox <gi...@apache.org> on 2021/06/24 14:17:44 UTC

[GitHub] [nifi] JonathanKessler commented on pull request #5061: NIFI-8523 Update secure ftp processors to make configurable which algorithms, ciphers and message authentication codes are allowed to be used by the SSH Client.

JonathanKessler commented on pull request #5061:
URL: https://github.com/apache/nifi/pull/5061#issuecomment-867674263


   > When attempting to verify the most recent updates at runtime, the `ListSFTP` worked as expected with the default blank values for the new properties. However, when specifying a value for `Ciphers Allowed`, NiFi marked the processor as invalid with the following message:
   > 
   > `'Ciphers Allowed' validated against 'aes256-cbc' is invalid because 'Ciphers Allowed' is not supported or has no Validator associated with it.`
   > 
   > It appears that recent updates to remove the default values also removed any kind of validator, but I missed that detail last time around. Based on previous comments and support for Expression Language, it seems like using StandardValidators.NON_EMPTY_EL_VALIDATOR would be a good option.
   
   Good catch but NON_EMPTY_EL_VALIDATOR ensures that EL is present. It's supported but not required Going with NON_BLANK_VALIDATOR.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org