hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brahma Reddy Battula (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4043) Namenode Kerberos Login does not use proper hostname for host qualified hdfs principal name.
Date Thu, 18 Oct 2012 05:02:04 GMT

    [ https://issues.apache.org/jira/browse/HDFS-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478670#comment-13478670
] 

Brahma Reddy Battula commented on HDFS-4043:
--------------------------------------------

HI Ahad thanks a lot for reply..

{quote}
<property>
<name>dfs.namenode.kerberos.principal</name>
<value>hdfs/n01.prod.company.com@company.com</value>
</property>
<property>
<name>dfs.namenode.kerberos.internal.spnego.principal</name>
<value>HTTP/n01.prod.company.com@company.com</value>
</property>
{quote}

two properties I had configured as

hdfs/hostname of machine@HADOOP.COM(RELAM)
HTTP/hostname of machine@HADOOP.COM

I added both principal's (hdfs/hostname of machine@HADOOP.COM and HTTP/hostname of machine@HADOOP.COM)
to KDC and generated keytab

but it's failing for HTTP/(IP of machine) which is not added in the KDC and then ticket is
failing like following while doing checkpoint..

Oct 04 03:07:43 host-*******-168 krb5kdc[24598](info): TGS_REQ (6 etypes {3 1 23 16 17 18})
*******.168: ISSUE: authtime 1349300202, etypes {rep=23 tkt=18 ses=23}, hdfs/hadoop@HADOOP.COM
for hdfs/hadoop@HADOOP.COM
Oct 04 03:07:43 host-*******-168 krb5kdc[24598](info): TGS_REQ (6 etypes {3 1 23 16 17 18})
*******.168: ISSUE: authtime 1349300202, etypes {rep=23 tkt=18 ses=23}, hdfs/hadoop@HADOOP.COM
for hdfs/hadoop@HADOOP.COM
Oct 04 03:07:43 host-*******-168 krb5kdc[24598](info): TGS_REQ (6 etypes {3 1 23 16 17 18})
*******.168: ISSUE: authtime 1349300202, etypes {rep=23 tkt=18 ses=23}, hdfs/hadoop@HADOOP.COM
for HTTP/*******.168@HADOOP.COM
Oct 04 03:07:43 host-*******-168 krb5kdc[24598](info): TGS_REQ (6 etypes {3 1 23 16 17 18})
*******.168: ISSUE: authtime 1349300202, etypes {rep=23 tkt=18 ses=23}, hdfs/hadoop@HADOOP.COM
for HTTP/*******.168@HADOOP.COM


Mostly your's and mine(HDP-3980) is same,I think...Since  KerberosAuthenticator.this*.url.getHost()
is always retunring IP of the machine and then principal coming like HTTP/(ip of the machine)..

Please correct me If I am wrong...


                
> Namenode Kerberos Login does not use proper hostname for host qualified hdfs principal
name.
> --------------------------------------------------------------------------------------------
>
>                 Key: HDFS-4043
>                 URL: https://issues.apache.org/jira/browse/HDFS-4043
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 2.0.0-alpha, 2.0.1-alpha, 2.0.2-alpha, 2.0.3-alpha
>         Environment: CDH4U1 on Ubuntu 12.04
>            Reporter: Ahad Rana
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The Namenode uses the loginAsNameNodeUser method in NameNode.java to login using the
hdfs principal. This method in turn invokes SecurityUtil.login with a hostname (last parameter)
obtained via a call to InetAddress.getHostName. This call does not always return the fully
qualified host name, and thus causes the namenode to login to fail due to kerberos's inability
to find a matching hdfs principal in the hdfs.keytab file. Instead it should use InetAddress.getCanonicalHostName.
This is consistent with what is used internally by SecurityUtil.java to login in other services,
such as the DataNode. 

--
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

Mime
View raw message