Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAKN1TpkKuuAb0czyAntbtDf8mQ0ihi-y_mZnaLkOmFW37jL3Tw@mail.gmail.com>
References: 
 <CAKN1TpkpEF995Mizzm3XzYjKZLPb9Xs09_b8vfW+=RSgwRQTgg@mail.gmail.com>
 <CAKN1TpkKuuAb0czyAntbtDf8mQ0ihi-y_mZnaLkOmFW37jL3Tw@mail.gmail.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Wed, 16 Mar 2016 17:03:40 +0100
Message-ID: 
 <CAGB5yNkBR5v5MyjxsY7mtW_zPmEHDNw=mRNqx2pwGTgsj2QU9A@mail.gmail.com>
Subject: Re: Enable ssl for kafka endpoints
To: dev <dev@camel.apache.org>
Content-Type: text/plain; charset=UTF-8

Hi Gerard

Okay sounds good. Let us know how it goes. Yeah Camel 2.17 has
migrated camel-kafka to use their new java library. So there is likely
a bunch of changes.

And if you find something not being able to configure SSL etc then let
us know. And maybe you can find out how to setup SSL with their java
library, and see if we miss anything in camel-kafka to allow that.

On Wed, Mar 16, 2016 at 1:35 PM, Gerard Klijs <gerard.klijs@dizzit.com> wrote:
> I'm now in the process of building the project from git, and I noticed it's
> already using the new consumer and properties. I will try it out to see if
> it works for me.
>
> On Wed, Mar 16, 2016 at 1:18 PM Gerard Klijs <gerard.klijs@dizzit.com>
> wrote:
>
>> The current version of the camel-kafka component already has the latest
>> released (0.9.0.1) kafka client included. To be able to use one of the new
>> features, mutual ssl authentication with the broker, the
>> current camel-kafka component needs some changes:
>> - Start using the new kafka consumer (), this changes a lot, different
>> properties are needed to create the connection, and a different mechanism
>> is used to subscribe to topics, and to get them.
>> - Allow at least 5 (preferably all) properties having to do with the ssl
>> configuration to be used for the ssl connection, both by the consumer and
>> the producer.
>>
>> I was wondering if anyone is thinking about doing this. We are currently
>> considering camel to connect non-java applications to our kafka cluster. We
>> are required to use ssl, both for the encryption, and for use with the
>> SimpleAclAuthorizer. It might be an option for us to do it ourselves and
>> summit the patch.
>>
>> I just started to take a look at camel, used it to read an xml, and send
>> it to kafka as avro, using the confluent schema registry.
>>


-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2