[
https://issues.apache.org/jira/browse/CAMEL-23505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-23505:
-------------------------------------
Fix Version/s: 4.14.8
4.18.3
4.21.0
> camel-splunk-hec: align hostname verification with system default in
> SplunkHECProducer
> --------------------------------------------------------------------------------------
>
> Key: CAMEL-23505
> URL: https://issues.apache.org/jira/browse/CAMEL-23505
> Project: Camel
> Issue Type: Bug
> Components: camel-splunk-hec
> Reporter: Andrea Cosentino
> Assignee: Federico Mariani
> Priority: Major
> Fix For: 4.14.8, 4.18.3, 4.21.0
>
>
> In {{SplunkHECProducer.doStart()}} (else-branch, around lines 78–85), the
> {{SSLConnectionSocketFactory}} is built with
> {{NoopHostnameVerifier.INSTANCE}}, which is inconsistent with
> {{skipTlsVerify=false}} (the default).
> {code:java}
> SSLConnectionSocketFactory sslsf
> = new SSLConnectionSocketFactory(endpoint.provideSSLContext(),
> NoopHostnameVerifier.INSTANCE);
> {code}
> The verifier should fall back to the system default in this branch:
> {code:java}
> SSLConnectionSocketFactory sslsf
> = new SSLConnectionSocketFactory(endpoint.provideSSLContext());
> {code}
> Optionally, expose an {{x509HostnameVerifier}} {{@UriParam}} on
> {{SplunkHECConfiguration}} so users can plug in a custom verifier (mirroring
> camel-http).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
