You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Evan Galpin (Jira)" <ji...@apache.org> on 2022/04/01 15:57:00 UTC

[jira] [Comment Edited] (BEAM-14000) Elastic search IO doesnot work when both username/password and keystore are used

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

Evan Galpin edited comment on BEAM-14000 at 4/1/22 3:56 PM:
------------------------------------------------------------

[~nishantjain91] that would be great, please go ahead! :)  -I'll assign to you- I believe a PMC member would first need to grant contributor permission in Jira before a ticket can be assigned, but don't let that stop you from working on it and opening a PR!


was (Author: egalpin):
[~nishantjain91] that would be great, please go ahead! :)  I'll assign to you

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