to
> > Kafka which uses all the Kafka ssl properties.
> >
> > Is that acceptable to resolve KAFKA-6654?
> > Can you think of a better solution?
> >
> >
> > -Original Message-
> > From: Colin McCabe [mailto:cmcc...@apache.org]
> > Sent: Monday,
ch uses all the Kafka ssl properties.
>
> Is that acceptable to resolve KAFKA-6654?
> Can you think of a better solution?
>
>
> -Original Message-
> From: Colin McCabe [mailto:cmcc...@apache.org]
> Sent: Monday, October 15, 2018 7:58 PM
> To: dev@kafka.apache.
Kafka ssl properties.
Is that acceptable to resolve KAFKA-6654?
Can you think of a better solution?
-Original Message-
From: Colin McCabe [mailto:cmcc...@apache.org]
Sent: Monday, October 15, 2018 7:58 PM
To: dev@kafka.apache.org
Subject: Re: KAFKA-6654 custom SSLContext
In general Kafk
ote:
> I am new to this mailing list. I am not sure what I should do next.
> Should I create a KIP to discuss this?
>
> -Original Message-
> From: Pellerin, Clement
> Sent: Wednesday, October 10, 2018 4:38 PM
> To: dev@kafka.apache.org
> Subject: KAFKA-6654 cust
I am new to this mailing list. I am not sure what I should do next. Should I
create a KIP to discuss this?
-Original Message-
From: Pellerin, Clement
Sent: Wednesday, October 10, 2018 4:38 PM
To: dev@kafka.apache.org
Subject: KAFKA-6654 custom SSLContext
KAFKA-6654 correctly states
KAFKA-6654 correctly states that there will never be enough configuration
parameters to fully configure the SSLContext/SSLSocketFactory created by Kafka.
For example, in our case, we need an alias to choose the key in the keystore,
and we need an implementation of OCSP.
KAFKA-6654 suggests to mak
