You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Chamikara Madhusanka Jayalath (Jira)" <ji...@apache.org> on 2022/03/17 17:44:00 UTC

[jira] [Commented] (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=17508338#comment-17508338 ] 

Chamikara Madhusanka Jayalath commented on BEAM-14000:
------------------------------------------------------

Do you think this is a validation error ? I'm not sure about the severity of the issue based on your description.

cc: [~egalpin] in case he has context.

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