kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gwen Shapira (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-1686) Implement SASL/Kerberos
Date Tue, 04 Nov 2014 17:44:34 GMT

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

Gwen Shapira commented on KAFKA-1686:
-------------------------------------

yes, +1 for a keytab for each broker as described by [~harsha_ch] and the renewTicket thread
design.

Authorization is a different issue (and separate JIRA), but I can imagine having a separate
"role" for brokers that lets them do anything on any topic.



> 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.9.0
>            Reporter: Jay Kreps
>            Assignee: Sriharsha Chintalapani
>             Fix For: 0.9.0
>
>
> 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)

Mime
View raw message