[
https://issues.apache.org/jira/browse/BEAM-14000?focusedWorklogId=754790&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-754790
]
ASF GitHub Bot logged work on BEAM-14000:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Apr/22 19:59
Start Date: 08/Apr/22 19:59
Worklog Time Spent: 10m
Work Description: egalpin commented on PR #17297:
URL: https://github.com/apache/beam/pull/17297#issuecomment-1093305644
@nishantjain91 I'm thinking it might be sufficient to test that calling
`ConnectionConfiguration#createClient` with username/password, ssl, and then
both set, would generate a RestClient with the expected settings configured.
That way we'll be testing the code that we have control over and not
SSL/Elasticsearch's configuration of SSL.
Issue Time Tracking
-------------------
Worklog Id: (was: 754790)
Time Spent: 1h 20m (was: 1h 10m)
> 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: 1h 20m
> 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)
