You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Edoardo Comar (JIRA)" <ji...@apache.org> on 2017/01/10 09:46:58 UTC
[jira] [Commented] (KAFKA-4611) Support custom authentication
mechanism
[ https://issues.apache.org/jira/browse/KAFKA-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814508#comment-15814508 ]
Edoardo Comar commented on KAFKA-4611:
--------------------------------------
Hi, I am not sure what you are asking is not covered already :
https://issues.apache.org/jira/browse/KAFKA-4292 proposes custom callback handlers (therefore you control how to check username and pwd).
https://issues.apache.org/jira/browse/KAFKA-4259 added the functionality of defining jaas configurations in the client config file.
https://issues.apache.org/jira/browse/KAFKA-4180 will add the functionality of allowing different jaas config in a single client process.
Please note that Kerberos login uses JAAS too.
> Support custom authentication mechanism
> ---------------------------------------
>
> Key: KAFKA-4611
> URL: https://issues.apache.org/jira/browse/KAFKA-4611
> Project: Kafka
> Issue Type: Improvement
> Components: clients
> Affects Versions: 0.10.0.0
> Reporter: mahendiran chandrasekar
>
> Currently there are two login mechanisms supported by kafka client.
> 1) Default Login / Abstract Login which uses JAAS authentication
> 2) Kerberos Login
> Supporting user defined login mechanism's would be nice.
> This could be achieved by removing the limitation from [here](https://github.com/apache/kafka/blob/0.10.0/clients/src/main/java/org/apache/kafka/common/security/authenticator/LoginManager.java#L44) ... Instead get custom login module implemented by user from the configs, gives users the option to implement custom login mechanism.
> I am running into an issue in setting JAAS authentication system property on all executors of my spark cluster. Having custom mechanism to authorize kafka would be a good improvement for me
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)