[
https://issues.apache.org/jira/browse/KAFKA-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708544#comment-14708544
]
Jun Rao commented on KAFKA-1686:
--------------------------------
[~sriharsha], in KAFKA-2210, [~parth.brahmbhatt] is extending KafkaPrincipal
with a principal type (e.g., user, group). With SASL, many people probably want
to do role based authorization management. Do you know typically how the role
information is passed in to the server? Do we get the role as part of the SASL
authentication of the client?
> 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)
