[
https://issues.apache.org/jira/browse/KAFKA-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708588#comment-14708588
]
Sriharsha Chintalapani commented on KAFKA-1686:
-----------------------------------------------
[~junrao] what you mean by role based authorization here. In Sasl you get
clients authorizationID which is a kerberos principal. In hadoop ( hdfs, hbase
& others) you take the principal and try to use pluggable group mapping service
to grab linux user group or ldap group and make authorization extend not just
to user but also group the user belongs to.
> 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
> 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)
