[
https://issues.apache.org/jira/browse/HADOOP-7510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113648#comment-13113648
]
Jitendra Nath Pandey commented on HADOOP-7510:
----------------------------------------------
> Fixed hftp/hsftp to return the correct uri with the correct port, but return
> a canonical service with the
> secure port (which strays from other filesystems).
What problems you ran into that compelled to use https port for service in
hftp file system? Earlier and for hdfs it uses rpc port. Rpc port is used,
because eventually its the Rpc port that is passed in TokenSelector to select a
token (from ipc.Client). Was it tested with secure hftp setup or is there a
different call flow that I am missing?
> Modified the getCanonicalService changes to be compatible with expectations
> of the TokenCache.
This method returns null for all the file systems that don't have a valid
authority. Why is this change required? This is a public API, I am
uncomfortable modifying it to return null for all file systems except hdfs,
hftp. TokenCache should work fine if a string is returned, it has been working
fine with strings so far.
> Tokens should use original hostname provided instead of ip
> ----------------------------------------------------------
>
> Key: HADOOP-7510
> URL: https://issues.apache.org/jira/browse/HADOOP-7510
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Fix For: 0.20.205.0
>
> Attachments: HADOOP-7510-10.patch, HADOOP-7510-2.patch,
> HADOOP-7510-3.patch, HADOOP-7510-4.patch, HADOOP-7510-5.patch,
> HADOOP-7510-6.patch, HADOOP-7510-8.patch, HADOOP-7510-9.patch,
> HADOOP-7510.patch
>
>
> Tokens currently store the ip:port of the remote server. This precludes
> tokens from being used after a host's ip is changed. Tokens should store the
> hostname used to make the RPC connection. This will enable new processes to
> use their existing tokens.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
