[jira] [Commented] (CAMEL-15075) camel-kafka - Configuration via SSLContextParameters does not work as expected

["Claus Ibsen (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CAMEL-15075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110014#comment-17110014 ] 

Claus Ibsen commented on CAMEL-15075:
-------------------------------------

Thanks can you check Camel 3.3.0 release.

If its still a problem then we should add a note that loading from classpath is a limitation in Kafka (Camel is just the facade on top). And that the location should be a file based resource.

> 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
>
> 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)