Github user ottobackwards commented on the issue:
https://github.com/apache/nifi/pull/2704
I found a bug in this in the aws implementation, I am not sure how you
would see it in the other processors, I found it when bringing this code into
my Gateway Api PR.
The issue is that customValidate validates that both host and port need to
be set, but not that both user and password need to be set.
Since I test for this ( from the InvokeHttp testProxy ), I fail.
---
