You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/09/03 06:13:47 UTC
[jira] [Commented] (KAFKA-1686) Implement SASL/Kerberos

    [ https://issues.apache.org/jira/browse/KAFKA-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728472#comment-14728472 ] 

ASF GitHub Bot commented on KAFKA-1686:
---------------------------------------

GitHub user harshach opened a pull request:

    https://github.com/apache/kafka/pull/191

    KAFKA-1686: Implement SASL/Kerberos.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/harshach/kafka KAFKA-1686-V1

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/191.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #191
    
----
commit 82737e5bb71f67271d90c059dede74935f8a5e56
Author: Sriharsha Chintalapani <ha...@hortonworks.com>
Date:   2015-08-31T23:07:15Z

    KAFKA-1686. Implement SASL/Kerberos.

commit a3417d7f2c558c0082799b117a3c62c706ad519d
Author: Sriharsha Chintalapani <ha...@hortonworks.com>
Date:   2015-09-03T03:31:34Z

    KAFKA-1686. Implement SASL/Kerberos.

commit 8f718ce6b03a9c86712dc8f960af2b739b8ed510
Author: Sriharsha Chintalapani <ha...@hortonworks.com>
Date:   2015-09-03T04:10:40Z

    KAFKA-1686. Implement SASL/Kerberos.

----


> Implement SASL/Kerberos
> -----------------------
>
>                 Key: KAFKA-1686
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1686
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: security
>    Affects Versions: 0.8.2.1
>            Reporter: Jay Kreps
>            Assignee: Sriharsha Chintalapani
>            Priority: Blocker
>             Fix For: 0.8.3
>
>
> Implement SASL/Kerberos authentication.
> To do this we will need to introduce a new SASLRequest and SASLResponse pair to the client protocol. This request and response will each have only a single byte[] field and will be used to handle the SASL challenge/response cycle. Doing this will initialize the SaslServer instance and associate it with the session in a manner similar to KAFKA-1684.
> When using integrity or encryption mechanisms with SASL we will need to wrap and unwrap bytes as in KAFKA-1684 so the same interface that covers the SSLEngine will need to also cover the SaslServer instance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)