Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/776
Ok, I built, ran contrib-check, started an instance, created a
`StandardSSLContextService` using `cacerts` as the truststore and a keystore
with different key and keystore passwords. Everything validated correctly and I
was able to use an `InvokeHTTP` processor with this controller service to
communicate with a remote HTTPS service. I did not have an existing service
which required client authentication, so I did not exercise that, but it is
existing functionality. If you've exercised this, I am ready to squash and
merge.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
