davsclaus opened a new pull request, #3256: URL: https://github.com/apache/camel-kamelets/pull/3256
Part of #3170: the Pulsar trust store, which waited on [CAMEL-27196](https://issues.apache.org/jira/browse/CAMEL-27196). **Draft until a Camel 4.24.0-SNAPSHOT with CAMEL-27196 is published.** The option came in with apache/camel#30350 on 2026-11-19 08:03 UTC; the newest published snapshot is from 2026-11-18 14:36 UTC. The validator checks every endpoint option against the Camel catalog, so CI fails until then. Built and tested locally against `camel-pulsar` and `camel-catalog` built from Camel main. ### What changed - `pulsar-source` and `pulsar-sink` take `tlsTrustCertsFilePath`: a PEM file with the certificate authorities to trust for a `pulsar+ssl://` broker, such as a private one, instead of the Java trust store. - Their `Good to know:` paragraph no longer says to set `javax.net.ssl.trustStore` because the Kamelet has no trust store option. It now says the certificate must be signed by an authority that Java trusts or one in `tlsTrustCertsFilePath`, and must be issued for the host name in `serviceUrl`. Camel 4.24 checks the host name by default (CAMEL-27207, in the Camel upgrade guide). ### Checked by running `camel run` with `pulsar-sink` → `pulsar-source`, against Apache Pulsar 5.0.1 standalone with TLS on 6651 and a broker certificate for `localhost`, signed by a private CA: | `serviceUrl` | `tlsTrustCertsFilePath` | Result | |---|---|---| | `pulsar+ssl://localhost:6651` | the CA's PEM file | both messages sent and received | | `pulsar+ssl://localhost:6651` | not set | `PKIX path building failed`, nothing received | | `pulsar+ssl://<another IP of the machine>:6651` | the CA's PEM file | `No subject alternative names matching IP address`, nothing received | `./mvnw clean install` passes against the local Camel snapshot and regenerated the library copy and the index. _Claude Code on behalf of Claus Ibsen_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
