[
https://issues.apache.org/jira/browse/HADOOP-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692432#comment-13692432
]
Sanjay Radia commented on HADOOP-9421:
--------------------------------------
bq. A clean solution to all these problems is tokens contain a server generated
opaque id. The server NEGOTIATE reports this id. The client looks for a token
with that id. Now no matter what interface/IP/hostname/proxy/NAT is used, the
client will always find the token.
Not sure how the above works. Is the "server generated opaque id" in a sense a
"logical principal" for he HA's service?
(BTW logical service authentication does work).
> Convert SASL to use ProtoBuf and provide negotiation capabilities
> -----------------------------------------------------------------
>
> 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
> Priority: Blocker
> Fix For: 3.0.0, 2.1.0-beta, 2.2.0
>
> Attachments: HADOOP-9421.patch, HADOOP-9421.patch, HADOOP-9421.patch,
> HADOOP-9421.patch, HADOOP-9421.patch, HADOOP-9421.patch, 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
