[
https://issues.apache.org/jira/browse/KAFKA-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987208#comment-14987208
]
Rajini Sivaram commented on KAFKA-2658:
---------------------------------------
[~junrao] We are clearly very near the deadline for Kafka 0.9.0.0 and
understand reluctance to include such a large patch, even though the majority
is test code. It is very important for us to be able to provide authentication
credentials using SASL but we do not use Kerberos. We were just wondering
whether it might be possible to include a minimal patch to allow SASL providers
to be plugged in on client and server. If that was acceptable we could provide
the patch today. If there is anything at all we could do to alleviate your
concerns on inclusion of this patch please let us know.
Failing that we look forward to working with you to accept the existing patch
for inclusion shortly after Kafka 0.9.0.0 branch is cut. Thank you...
> Implement SASL/PLAIN
> --------------------
>
> Key: KAFKA-2658
> URL: https://issues.apache.org/jira/browse/KAFKA-2658
> Project: Kafka
> Issue Type: Sub-task
> Components: security
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
> Priority: Critical
> Fix For: 0.9.0.0
>
>
> KAFKA-1686 supports SASL/Kerberos using GSSAPI. We should enable more SASL
> mechanisms. SASL/PLAIN would enable a simpler use of SASL, which along with
> SSL provides a secure Kafka that uses username/password for client
> authentication.
> SASL/PLAIN protocol and its uses are described in
> [https://tools.ietf.org/html/rfc4616]. It is supported in Java.
> This should be implemented after KAFKA-1686. This task should also hopefully
> enable simpler unit testing of the SASL code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
