[ https://issues.apache.org/jira/browse/NIFI-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625277#comment-14625277 ]
ASF subversion and git services commented on NIFI-762: ------------------------------------------------------ Commit 8bd20510ee348e497b6039e083b32e37a4d3a20e in incubator-nifi's branch refs/heads/develop from [~markap14] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=8bd2051 ] NIFI-762: Allow user to set keystore and truststore properties instead of setting sslcontext > Site-to-site client config implements Serializable but has non-Serializable > member variable > ------------------------------------------------------------------------------------------- > > Key: NIFI-762 > URL: https://issues.apache.org/jira/browse/NIFI-762 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build > Reporter: Mark Payne > Assignee: Mark Payne > Fix For: 0.3.0 > > Attachments: > 0001-NIFI-762-Allow-user-to-set-keystore-and-truststore-p.patch > > > Right now, if we want to use the site-to-site client securely, we set the > SSLContext on the configuration object. However, SSLContext is not > serializable. It is important, however, to be able to set an SSLContext, > rather than providing keystore and truststore properties directly. > As a result, I suggest we implement both a Serializable form of the > configuration and a non-serializable form. The non-serializable form can be > configured with SSLContext while the serializable form would be configured > with keystore and truststore filename, type, and password. -- This message was sent by Atlassian JIRA (v6.3.4#6332)