[
https://issues.apache.org/jira/browse/CAMEL-22321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18012530#comment-18012530
]
Andrea Cosentino commented on CAMEL-22321:
------------------------------------------
The release should be in September.
It's not possible to backport IMO, because this change the behavior. 4.13 or
4.12 are not LTS release, the LTS active branch is 4.10.x and we didn't plan to
backport there, only if this was a bug it could be the case, but it's not.
We could release a 4.14.0 Camel Kafka Connector release, after Camel Kamelets
release. But there is no ETA for this.
> OpenSearch SSL Fallback Issue
> -----------------------------
>
> Key: CAMEL-22321
> URL: https://issues.apache.org/jira/browse/CAMEL-22321
> Project: Camel
> Issue Type: Improvement
> Components: camel-opensearch
> Reporter: Sanket
> Assignee: Andrea Cosentino
> Priority: Minor
> Fix For: 4.14.0
>
>
> Problem:
> The OpenSearch component's SSL configuration lacks a fallback mechanism to
> the default JVM SSL context when SSL context creation fails or returns null.
> This is inconsistent with other Camel components like HTTP which have proper
> fallback handling.
> {code:java}
> if (ObjectHelper.isNotEmpty(configuration.getCertificatePath())) {
> final TlsStrategy tlsStrategy =
> ClientTlsStrategyBuilder.create()
> .setSslContext(createSslContextFromCa())
>
> .setHostnameVerifier(configuration.getHostnameVerifier())
> .setTlsDetailsFactory(
> sslEngine -> new
> TlsDetails(sslEngine.getSession(), sslEngine.getApplicationProtocol()))
> .build();
> }{code}
> If certificate is empty we are not using any TlsStrategy.
> we should fallback to JVM's default ssl config incase custom CA is not
> provided.
> {code:java}
> return SSLContext.getDefault(); {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
