Hi Tao, I have a couple of questions:
1. Is there a reason why you wouldn't want to implement a custom SASL mechanism to use your authentication mechanism? SASL itself aims to provide pluggable authentication mechanisms. 2. The KIP suggests that you are interested in plugging in a custom authenticator, but not a custom transport layer. If that is the case, maybe you need CUSTOM_PLAINTEXT and CUSTOM_SSL for consistency with the other security protocols (which are a combination of transport layer protocol and authentication protocol)? Regards, Rajini On Tue, Jan 26, 2016 at 6:58 AM, tao xiao <xiaotao...@gmail.com> wrote: > HI Kafka developers, > > I raised a KIP-44, allow a customized security protocol, for discussion. > The goal of this KIP to enable a customized security protocol where users > can plugin their own implementation. > > Feedback is welcomed > >
