[
https://issues.apache.org/jira/browse/HADOOP-9296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876615#comment-13876615
]
Alejandro Abdelnur commented on HADOOP-9296:
--------------------------------------------
[~daryn], you stated "The root cause is the client "guesses" the principal for
a remote NN based on the principal of its default NN.", wouldn't the approach
like the one you doing for HTTP SPNEGO, in HADOOP-10158, work for RPC as well?
Then we would not need the servers to advertise their principal at all, no?
> Authenticating users from different realm without a trust relationship
> ----------------------------------------------------------------------
>
> Key: HADOOP-9296
> URL: https://issues.apache.org/jira/browse/HADOOP-9296
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Reporter: Benoy Antony
> Assignee: Benoy Antony
> Attachments: HADOOP-9296-1.1.patch, HADOOP-9296.patch,
> HADOOP-9296.patch, multirealm.pdf
>
>
> Hadoop Masters (JobTracker and NameNode) and slaves (Data Node and
> TaskTracker) are part of the Hadoop domain, controlled by Hadoop Active
> Directory.
> The users belong to the CORP domain, controlled by the CORP Active Directory.
> In the absence of a one way trust from HADOOP DOMAIN to CORP DOMAIN, how will
> Hadoop Servers (JobTracker, NameNode) authenticate CORP users ?
> The solution and implementation details are in the attachement
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
