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

Aaron T. Myers commented on HADOOP-9019:
----------------------------------------

bq. In a private cluster where machines dont have any DNS server and also 
mapping of all ip/hostnames may not be present in /etc/hosts. In that case we 
may need to use IP instead of hostname in configs.

But how will this proposal help in such a situation? In order for this to work, 
the cluster will have to be able to do reverse name lookups on the IP address, 
so properly configured DNS of some sort (either a DNS server or populated 
/etc/hosts) will have to be present.
                
> KerberosAuthenticator.doSpnegoSequence(..) should create a HTTP principal 
> with hostname everytime 
> --------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-9019
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9019
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Vinay
>
> in KerberosAuthenticator.doSpnegoSequence(..) following line of code will 
> just create a principal of the form "HTTP/<host>",
> {code}            String servicePrincipal = 
> KerberosUtil.getServicePrincipal("HTTP",
>                 KerberosAuthenticator.this.url.getHost());{code}
>  but uri.getHost() is not sure of always getting hostname. If uri contains 
> IP, then it just returns IP.
> For SPNEGO authentication principal should always be created with <hostname>.
> This code should be something like this, which will look /etc/hosts to get 
> hostname
> {code}            String hostname = InetAddress.getByName(
>                 KerberosAuthenticator.this.url.getHost()).getHostName();
> String servicePrincipal = KerberosUtil.getServicePrincipal("HTTP",
>                 hostname);{code}

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

Reply via email to