[
https://issues.apache.org/jira/browse/HADOOP-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655459#comment-13655459
]
Luke Lu commented on HADOOP-9421:
---------------------------------
Looks like we need to limit the scope of this jira, which is a subtask of the
RPC cleanup, as Sanjay, who owns parent JIRA told me via email that they would
like to start a scale test with the new RPC v9 ASAP. I think that as long as we
have a mechanism to evolve SASL mechanisms/protocols negotiation without
breaking general RPC backward compatibility, we can finish the generic SASL
support in a separate JIRA, say the original HADOOP-9034.
My proposal for this JIRA would be:
* Remove the AuthMethod byte (which will be covered by the SaslRequestPoto
later)
* Add SaslRequestProto (with a required version field and a optional token
field) and SaslResponseProto (optional status, token, error fields).
* Prefix Sasl*Proto with int32 like the rest of the RPC.
Thoughts?
> Generalize SASL Support with Protocol Buffer
> --------------------------------------------
>
> 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
>
>
--
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
