[
https://issues.apache.org/jira/browse/THRIFT-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904024#action_12904024
]
David Reiss commented on THRIFT-876:
------------------------------------
> Where do we draw the line?
That's a good question, and, unfortunately, I don't have a good answer. The
design of Thrift is such that almost all of the concrete classes (servers,
protocols, and transports) could be moved out of the core and into separate
modules and the system would work just fine. My intuition just tells me that
SASL is not a core part of RPC.
If you want to move ahead with this, I could be okay with it. If this is going
to be committed to the main tree, I think it's necessary to have a definition
of the "Thrift with SASL" protocol outside of the Java source, specifically the
"profiling requirements" specified by the SASL RFC
(http://www.ietf.org/rfc/rfc2222.txt). I think 2 and 3 are the most important.
I set up http://wiki.apache.org/thrift/ThriftIntegrationConventions for
documenting this sort of thing, or it could just go in a text file under doc.
> Add SASL support
> ----------------
>
> Key: THRIFT-876
> URL: https://issues.apache.org/jira/browse/THRIFT-876
> Project: Thrift
> Issue Type: New Feature
> Components: Java - Library
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Attachments: thrift-876.txt, thrift-876.txt.2
>
>
> It'd be nice if there were some way of securing Thrift communication in a
> pluggable fashion. SASL is the implementation chosen by Hadoop for this.
> Seems like a good option for Thrift, too.
> I'll start with a Java implementation, then move on to support the other
> language bindings.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
