[
https://issues.apache.org/jira/browse/NIFI-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406630#comment-15406630
]
ASF GitHub Bot commented on NIFI-2466:
--------------------------------------
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.
> SSLContextService should support specifying Key Password
> --------------------------------------------------------
>
> Key: NIFI-2466
> URL: https://issues.apache.org/jira/browse/NIFI-2466
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> Currently, the SSLContextService supports only a keystore password and
> assumes that the key password is the same. We should support setting a
> separate password for the key itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
