You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@storm.apache.org by "Raghavendra Nandagopal (JIRA)" <ji...@apache.org> on 2014/06/20 01:22:24 UTC

[jira] [Commented] (STORM-348) (Security) Netty SASL Authentication

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

Raghavendra Nandagopal commented on STORM-348:
----------------------------------------------

Please assign it to me.  I am taking a look at it.

> (Security) Netty SASL Authentication
> ------------------------------------
>
>                 Key: STORM-348
>                 URL: https://issues.apache.org/jira/browse/STORM-348
>             Project: Apache Storm (Incubating)
>          Issue Type: Bug
>            Reporter: Robert Joseph Evans
>              Labels: security
>
> Currently The Netty transport does no authentication at all.  You can encrypt the tuples being sent, but that is a huge performance hit for many cases that do not need it.  We should support simple SASL authentication when Netty first connects to an external process.  We probably want to use something similar to what we do for ZK, and generate a random secret for each topology.



--
This message was sent by Atlassian JIRA
(v6.2#6252)