[
https://issues.apache.org/jira/browse/CAMEL-22321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18012529#comment-18012529
]
Sanket commented on CAMEL-22321:
--------------------------------
Hi team,
Thanks for the improvement! I wanted to check on two things:
# *Is there a planned release date for Camel 4.14.0?*
# *Is it possible to backport this improvement to an earlier version* (e.g.,
4.13.x or 4.12.x) if it's compatible?
We would benefit from this enhancement in production but are currently running
an earlier 4.x version.
Please let me know if backporting is feasible or if a patch could be proposed.
Thanks again for the great work!
cc: [~acosentino] [~davsclaus]
> 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)
