[jira] [Commented] (NIFI-762) Site-to-site client config implements Serializable but has non-Serializable member variable

["Aldrin Piri (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625131#comment-14625131 ] 

Aldrin Piri commented on NIFI-762:
----------------------------------

Build looks good and the serialized form is, as advertised, serializable with the alternative construction.  Contrib passes. +1

> 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)