[ 
https://issues.apache.org/jira/browse/HADOOP-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daryn Sharp updated HADOOP-9421:
--------------------------------

    Attachment: HADOOP-9421.patch

I scaled back my patch to the simplest skeleton implementation.  The highlights 
are:
* SASL is very stateful
* SASL is wrapped with RPC header like normal requests to facility dynamic 
decoding
* Client can correctly handle RPC exceptions during SASL negotiation
* Server advertises SASL mechs to client

Deficiencies to be addressed in another jira:
* RPC client still pre-instantiates a SASL client and blindly uses it - instead 
of using the server advertisement
* RPC server is also pre-creating a SASL server
* Protocol and serverId not included in the SASL mech advertisement or the 
client initiate

Code cleanups:
* RPC client loop for SASL and normal operation should be folded together 
simplify and reduce redundant code
* RPC server decoding paths for connect/sasl/rpc can be greatly simplified - 
the existing impl is already a twisty maze

I've started on some of the cleanup, but I wanted to get a functional patch to 
unblock the start of v9 testing, and that I can use as a base for work of a 
larger scope.


                
> 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: Daryn Sharp
>         Attachments: HADOOP-9421.patch, 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

Reply via email to