You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "nishant jain (Jira)" <ji...@apache.org> on 2022/02/25 09:59:00 UTC
[jira] [Updated] (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:all-tabpanel ]
nishant jain updated BEAM-14000:
--------------------------------
Description:
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
was:
When using both username/password and ssl keystore, ElasticSearchIO doesnot Create correct restclient.
Firstly, it sets HttpClientConfigCallback using httpAsyncClientBuilder if username and passowrd is use. Aterwars, it will replace HttpClientConfigCallback to httpClientBuilder is ssl store is used, hence losing the credentials provider
> 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)