[
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
The IpSerializationType change is orthogonal to this patch, so I'd like to
defer to another jira if that's ok?
I changed the authMethod in the connection header to specify the authentication
protocol - in this case none, or sasl, to allow for future protocols. I think
that's what you wanted? It also let me handle the funky switch to simple in a
cleaner fashion.
I did realize that having the mechanism/proto/serverId tuple is insufficient.
Those are really just the fields required to create the SASL server or client,
which is independent of what we're actually authenticating. Ex. It's not right
to assume DIGEST-MD5 means token, when perhaps SCRAM would be a better
replacement. So now I'm passing TOKEN/DIGEST-MD5/... so that some happy day in
the future, we can configure the mechanisms for different auth types, and the
auth types are a step closer to pluggable.
> 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.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
