[
https://issues.apache.org/jira/browse/HDFS-14375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16904220#comment-16904220
]
Wei-Chiu Chuang edited comment on HDFS-14375 at 8/9/19 10:18 PM:
-----------------------------------------------------------------
Thanks for reporting the issue, [~Jihyun.Cho].
But I am not sure – I thought this can be addressed by setting up a proper
auth_to_local rule?
{quote}The patch checks only using username and hostname except realm.
{quote}
This is most likely not the right way to solve the problem.
[~eyang] FYI.
was (Author: jojochuang):
Thanks for reporting the issue, [~Jihyun.Cho].
But I am not sure -- I thought this can be addressed by setting up a proper
auth_to_local rule?
[~eyang] FYI.
> DataNode cannot serve BlockPool to multiple NameNodes in the different realm
> ----------------------------------------------------------------------------
>
> Key: HDFS-14375
> URL: https://issues.apache.org/jira/browse/HDFS-14375
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: security
> Affects Versions: 3.1.1
> Reporter: Jihyun Cho
> Assignee: Jihyun Cho
> Priority: Major
> Attachments: authorize.patch
>
>
> Let me explain the environment for a description.
> {noformat}
> KDC(TEST1.COM) <-- Cross-realm trust --> KDC(TEST2.COM)
> | |
> NameNode1 NameNode2
> | |
> ---------- DataNodes (federated) ----------
> {noformat}
> We configured the secure clusters and federated them.
> * Principal
> ** NameNode1 : nn/[email protected]
> ** NameNode2 : nn/[email protected]
> ** DataNodes : dn/[email protected]
> But DataNodes could not connect to NameNode1 with below error.
> {noformat}
> WARN
> SecurityLogger.org.apache.hadoop.security.authorize.ServiceAuthorizationManager:
> Authorization failed for dn/[email protected]
> (auth:KERBEROS) for protocol=interface
> org.apache.hadoop.hdfs.server.protocol.DatanodeProtocol: this service is only
> accessible by dn/[email protected]
> {noformat}
> We have avoided the error with attached patch.
> The patch checks only using {{username}} and {{hostname}} except {{realm}}.
> I think there is no problem. Because if realms are different and no
> cross-realm setting, they cannot communication each other. If you are worried
> about this, please let me know.
> In the long run, it would be better if I could set multiple realms for
> authorize. Like this;
> {noformat}
> <property>
> <name>dfs.namenode.kerberos.trust-realms</name>
> <value>TEST1.COM,TEST2.COM</value>
> </property>
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
