[
https://issues.apache.org/jira/browse/BEAM-10838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17370826#comment-17370826
]
Andrew Boshardy edited comment on BEAM-10838 at 6/28/21, 8:00 PM:
------------------------------------------------------------------
This is something that would be very useful for us. As it is now, I'm having a
lot of trouble getting the keystorePath to work at all, let alone well.
PS: If you have an example of how to package the keystore so you can use it on
a distributed runner like GCP Dataflow, that would be _much_ appreciated!
was (Author: dboshardy):
This is something that would be very useful for us. As it is now, I'm having a
lot of trouble getting the keystorePath to work at all, let alone well.
> Add a withSSLContext builder method to ElasticsearchIO
> -------------------------------------------------------
>
> Key: BEAM-10838
> URL: https://issues.apache.org/jira/browse/BEAM-10838
> Project: Beam
> Issue Type: Improvement
> Components: io-java-elasticsearch
> Reporter: Conor Landry
> Priority: P3
>
> Currently, the ElasticsearchIO transforms 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.3.4#803005)
