I'd like to proceed with SASL implementation enhancement:
https://issues.apache.org/jira/browse/KAFKA-4874
As this feature introduces new configuration parameter, I think KIP
would be of use.
Is there any chance I can get permissions to wiki in order to create
KIP document?
Provided it is accepted,
Thanks for filing the JIRA and checking KAFKA-3866. I'll try to add tests
to the PR so that we can merge it.
Ismael
On Thu, Mar 9, 2017 at 10:44 AM, Paweł Tomasik wrote:
> Ismael
>
> Thank you for the response
> I've walked through changes for KAFKA-3866.
> I think it shall fix the case I menti
Ismael
Thank you for the response
I've walked through changes for KAFKA-3866.
I think it shall fix the case I mentioned.
As for server side, I've added a jira wish issue:
https://issues.apache.org/jira/browse/KAFKA-4874
I'm working on project with high security restrictions, so I need to
find an
Hi Pawel,
It is by design that authentication is only performed during connection
establishment in the broker. Kafka relies on long-lived connections, which
means that another mechanism is needed to handle users who have been
removed from the system. A typical approach is to remove all ACLs for th
Hi
I've found a security issue in the kafka SASL implementation.
It seems that ticket refreshments are not necessary to keep
client-broker connection up.
Test scenario:
Client sucessfully connects to the broker using SASL_SSL security
protocol. Kerberos server is provided by Windows Server 2012 an
