[
https://issues.apache.org/jira/browse/CAMEL-15075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110301#comment-17110301
]
Claus Ibsen commented on CAMEL-15075:
-------------------------------------
Okay so it looks like it just uses the SSLContextParameters as parameters to
set them via that. And then copy its configuration into karaf configuration.
So can you provide more details what you think is wrong such as sample code,
configuration, a reproducer etc.
> camel-kafka - Configuration via SSLContextParameters does not work as expected
> ------------------------------------------------------------------------------
>
> Key: CAMEL-15075
> URL: https://issues.apache.org/jira/browse/CAMEL-15075
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka
> Affects Versions: 3.2.0
> Reporter: Peter Kullmann
> Priority: Major
> Fix For: 3.4.0
>
>
> The ssl parameters in kafka can be set using a camel SSLContextParameter
> object (see CAMEL-10705). But it doesn't work as expected.
> Camel allows many ways to specify a keystore location, ie a file path, a
> class path or an URL of the resource. Camel tries all possible ways to read
> the keystore. (Eg
> SSLContextParameters.getTrustManagers().getKeyStore().getResource()).
> For kafka this resolution doesn't take place. Kafka receives just the raw
> resource string (org.apache.camel.component.kafka.KafkaConfiguration:511):
>
> {code:java}
> addPropertyIfNotNull(props, SslConfigs.SSL_TRUSTSTORE_LOCATION_CONFIG,
> keyStore.getResource());
> {code}
> Kafka has a different expectation on this location from camel. In particular
> setting the camel keystore resource to a classpath location doesn't work for
> kafka (see also KAFKA-7685 for an attempt to support classpath resources).
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
