[
https://issues.apache.org/jira/browse/STORM-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raghavendra Nandagopal updated STORM-348:
-----------------------------------------
Attachment: Storm-Netty Authentication.pdf
Hi Bobby,
I have attached the changes that describes the implementation of SASL
mechanism for Storm-Netty. When you get a chance, Can you please review it?
The code changes are completed and I have tested with topology user as the
credentials to the SASL.
I need to know where I can get the kerberos token for a specific topology
from the Java code. Once this change is done, I can send you the pull request
within couple of days.
Thanks,
Raghavendra Nandagopal
> (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
> Assignee: Raghavendra Nandagopal
> Labels: security
> Attachments: Storm-Netty Authentication.pdf
>
>
> 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)
