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

Joe Stein commented on KAFKA-1477:
----------------------------------

Jun, 

Getting this to work in the new (java) client is going to take some more work 
integrating a secure nio version. Ivan is going to start later next week on 
that after this last configuration item is done. I created separate tickets 
KAFKA-1690 and KAFKA-1691 for the new (java) client work. 

I am +1 to committing this patch to trunk after the server configuration item 
is done and working how folks expect. This gives the broker support so we can 
start to get the existing clients (including third party clients e.g. 
https://github.com/Shopify/sarama/pull/156 ) to hook in now for security 
features as we are moving ahead with them overall. I see the existing (scala 
and third party) clients as stable clients we are incrementally changing to 
confirm compatibility with each other, the broker and new (java) clients too.  
We can drop support once they are not being used and folks have upgraded (or on 
an upgrade path at least) but I don't think we are there yet so putting this in 
now make sense.

> add authentication layer and initial JKS x509 implementation for brokers, 
> producers and consumer for network communication
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-1477
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1477
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Joe Stein
>            Assignee: Ivan Lyutov
>             Fix For: 0.8.3
>
>         Attachments: KAFKA-1477-binary.patch, KAFKA-1477.patch, 
> KAFKA-1477_2014-06-02_16:59:40.patch, KAFKA-1477_2014-06-02_17:24:26.patch, 
> KAFKA-1477_2014-06-03_13:46:17.patch, KAFKA-1477_trunk.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to