[
https://issues.apache.org/jira/browse/CAMEL-27196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-27196:
--------------------------------
Fix Version/s: 4.18.6
> camel-pulsar - add an option for a custom CA trust store file
> -------------------------------------------------------------
>
> Key: CAMEL-27196
> URL: https://issues.apache.org/jira/browse/CAMEL-27196
> Project: Camel
> Issue Type: Improvement
> Components: camel-pulsar
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.18.6, 4.24.0
>
>
> h3. Background
> When the endpoint creates its own {{PulsarClient}},
> {{PulsarEndpoint.doStart()}} sets only {{serviceUrl}} and the authentication
> ({{authenticationClass}}, {{authenticationParams}}). There is no endpoint or
> component option for the TLS settings of the client, so a broker on
> {{pulsar+ssl://}} whose certificate is signed by a private CA can only be
> used:
> * with a {{pulsarClient}} bean built in code, or
> * by changing the trust store of the whole JVM
> ({{-Djavax.net.ssl.trustStore=...}}).
> The Kamelets {{pulsar-source}} and {{pulsar-sink}} cannot offer a trust store
> option because of this, as a Kamelet cannot create the client bean; they
> document the JVM trust store instead.
> h3. Suggested improvement
> Add options to {{PulsarConfiguration}} and pass them to the {{ClientBuilder}}
> in {{PulsarEndpoint.doStart()}}:
> * {{tlsTrustCertsFilePath}}: PEM file with the CA certificates
> ({{ClientBuilder.tlsTrustCertsFilePath}});
> * optionally the trust store form: {{useKeyStoreTls}}, {{tlsTrustStoreType}},
> {{tlsTrustStorePath}}, {{tlsTrustStorePassword}} (marked secret);
> * optionally the client certificate for mutual TLS
> ({{tlsCertificateFilePath}}, {{tlsKeyFilePath}}).
> Only set them on the builder when they are configured, so the client defaults
> stay as they are. They have no effect when a {{pulsarClient}} is given.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)