[
https://issues.apache.org/jira/browse/BEAM-14000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508367#comment-17508367
]
nishant jain edited comment on BEAM-14000 at 3/17/22, 6:17 PM:
---------------------------------------------------------------
I am not sure what validation error means here?
This issue basically hinders pipleine from authencating with elastic cluster if
both username/password and sslcontext is used.
Regarding https://issues.apache.org/jira/browse/BEAM-10838, it will greatly
help in simplyfying ssl context building, but it will not resolve the bug here
as it is still replacing httpclientconfigcallback in createClient function
was (Author: JIRAUSER285800):
I am not sure what validation error means here?
This issue basically hinders pipleine from authencating with elastic cluster if
both username/password and sslcontext is used.
Regarding https://issues.apache.org/jira/browse/BEAM-10838, it will greatly
help in simplyfying sal context building, but it will not resolve the bug here
as it is still replacing httpclientconfigcallback in createClient function
> Elastic search IO doesnot work when both username/password and keystore are
> used
> --------------------------------------------------------------------------------
>
> Key: BEAM-14000
> URL: https://issues.apache.org/jira/browse/BEAM-14000
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: nishant jain
> Priority: P2
>
> When using both username/password and ssl keystore, ElasticSearchIO doesnot
> Create correct restclient.
>
> Firstly, it sets HttpClientConfigCallback using httpAsyncClientBuilder if
> username and passowrd is used. Afterwards, it will replace
> HttpClientConfigCallback to httpClientBuilder is ssl store is used, hence
> losing the credentials provider
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
