[
https://issues.apache.org/jira/browse/LOG4J2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246629#comment-16246629
]
Frank Swanson commented on LOG4J2-2072:
---------------------------------------
Thank you. Glad that worked out.
I have opened LOG4J2-2113 for the builder work. when this ticket is closed I
can work on that unless someone has already picked up.
> Support TLS configuration through FlumeAppender
> -----------------------------------------------
>
> Key: LOG4J2-2072
> URL: https://issues.apache.org/jira/browse/LOG4J2-2072
> Project: Log4j 2
> Issue Type: Bug
> Components: Flume Appender
> Affects Versions: 2.9.1
> Reporter: Frank Swanson
>
> When using the FlumeAppnder with a FlumeAvroManager it would be nice to be
> able to pass some properties through to the connect method for the RpcClient
> to support SSL configuration.
> The required properties to support the configuration are ~
> properties[0] =
> Property.createProperty(RpcClientConfigurationConstants.CONFIG_TRUST_ALL_CERTS,
> "false");
> properties[1] =
> Property.createProperty(RpcClientConfigurationConstants.CONFIG_SSL, "true");
> properties[2] =
> Property.createProperty(RpcClientConfigurationConstants.CONFIG_TRUSTSTORE,
> path_to_truststore);
> properties[3] =
> Property.createProperty(RpcClientConfigurationConstants.CONFIG_TRUSTSTORE_PASSWORD,
> super_secret);
> properties[4] =
> Property.createProperty(RpcClientConfigurationConstants.CONFIG_TRUSTSTORE_TYPE,
> "JKS");
> I am happy to provide a PR for this feature if supported.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
