[
https://issues.apache.org/jira/browse/THRIFT-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904342#action_12904342
]
Aaron T. Myers commented on THRIFT-876:
---------------------------------------
bq. I agree that we should address those requirements in a doc. Parts 1 (define
the "service name") and 5 (define how authorization is to be interpreted) seem
to be inapplicable to Thrift, since really the implementing service should
define those things. But the other parts seem useful - especially part 3, which
might not be addressed by the current patch - there should be some status codes
preceding each part of the SASL handshake in order to pass back a useful error
message for failure cases.
Sounds good. I'll work on a proposal for a (very tiny) "Thrift with SASL"
protocol.
> 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, thrift-876.txt.3
>
>
> 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.
