You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/04/06 12:46:00 UTC
[jira] [Work logged] (BEAM-14000) Elastic search IO doesnot work when both username/password and keystore are used
[ https://issues.apache.org/jira/browse/BEAM-14000?focusedWorklogId=753355&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-753355 ]
ASF GitHub Bot logged work on BEAM-14000:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 06/Apr/22 12:45
Start Date: 06/Apr/22 12:45
Worklog Time Spent: 10m
Work Description: asf-ci commented on PR #17297:
URL: https://github.com/apache/beam/pull/17297#issuecomment-1090227102
Can one of the admins verify this patch?
Issue Time Tracking
-------------------
Worklog Id: (was: 753355)
Time Spent: 0.5h (was: 20m)
> 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
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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)