[
https://issues.apache.org/jira/browse/HADOOP-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13662065#comment-13662065
]
Daryn Sharp commented on HADOOP-9421:
-------------------------------------
I am getting close to having a patch ready today/tomorrow, but it is based on
adding SASL into the RPC protocol to make the RPC handling much simpler.
Currently the client and/or server goes into a separate mode to handle SASL.
They assume either a SASL or RPC response in those modes, but if it gets the
other response it will fail with a decode error.
Wrapping SASL in the RPC header also allows makes it easy for the server to
issue challenges at times other than initial connection - ex. to demand the a
proposed capability token you've described. Or if a client uses a token to
connect and tries to request another token, the server could demand non-token
SASL auth instead of outright failing.
If you feel strongly, I can undo it.
> Convert SASL to use ProtoBuf and add lengths for non-blocking processing
> ------------------------------------------------------------------------
>
> Key: HADOOP-9421
> URL: https://issues.apache.org/jira/browse/HADOOP-9421
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: 2.0.3-alpha
> Reporter: Sanjay Radia
> Assignee: Junping Du
> Attachments: HADOOP-9421.patch, HADOOP-9421-v2-demo.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
