[
https://issues.apache.org/jira/browse/BEAM-10838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17479073#comment-17479073
]
Conor Landry commented on BEAM-10838:
-------------------------------------
Thanks for all of the interest. I can put together a pull request over the next
few weeks and +1 [~egalpin] 's idea for the implementation.
[~kenn] it could be tough to serialize a SSLContext/SSLContextBuilder and a
workaround could involve creating a factory or wrapper around SSLContextBuilder
limiting it's usage. Ignite has a [similar pattern
|https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/ssl/SslContextFactory.html]that
could be of interest.
> Add a withSSLContext builder method to ElasticsearchIO
> -------------------------------------------------------
>
> Key: BEAM-10838
> URL: https://issues.apache.org/jira/browse/BEAM-10838
> Project: Beam
> Issue Type: New Feature
> Components: io-java-elasticsearch
> Reporter: Conor Landry
> Priority: P2
>
> Currently, the ElasticsearchIO transforms have only one way to securely
> read/write Elasticsearch by using the withKeystorePath builder method and
> providing the location of a keystore containing a client key in jks format.
> This is a bit limiting, especially for Elasticsearch users not depending on
> shield to secure their clusters. I'd like to propose the addition of the
> builder method withSSLContext(SSLContext sslContext, which delegates to
> `httpClientBuilder.setSSLContext`.
> If this is (y), I can start working on it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
