kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mahendiran chandrasekar (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (KAFKA-4611) Support custom authentication mechanism
Date Wed, 11 Jan 2017 20:28:16 GMT

     [ https://issues.apache.org/jira/browse/KAFKA-4611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

mahendiran chandrasekar resolved KAFKA-4611.
--------------------------------------------
       Resolution: Workaround
    Fix Version/s: 0.10.2.0

> 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
>             Fix For: 0.10.2.0
>
>
> 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)

Mime
View raw message