jamesnetherton commented on issue #9185:
URL: https://github.com/apache/camel-quarkus/issues/9185#issuecomment-5726232529
Thanks for reporting this.
Unfortunately, there's a limitation / bug for some components that read
`KeyStoreParameters` in order to pass a keystore path and password to a
third-party client library.
Instead of handing the bridged bean to `camel-kafka` via
`sslContextParameters`, let the Kafka client resolve the Quarkus TLS
configuration itself through Kafka's `ssl.engine.factory.class` SPI. Quarkus
ships an implementation for this scenario:
On the Kafka endpoint do:
```java
kafka:your-topic
?securityProtocol=SSL
&additionalProperties.ssl.engine.factory.class=io.quarkus.kafka.client.tls.QuarkusKafkaSslEngineFactory
&additionalProperties.tls-configuration-name=kafka-tls
```
TLS config:
```properties
quarkus.tls.kafka-tls.key-store.p12.path=/path/to/keystore.p12
quarkus.tls.kafka-tls.key-store.p12.password=changeit
quarkus.tls.kafka-tls.trust-store.p12.path=/path/to/truststore.p12
quarkus.tls.kafka-tls.trust-store.p12.password=changeit
```
--
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]
