[
https://issues.apache.org/jira/browse/HDFS-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713109#comment-13713109
]
Jitendra Nath Pandey commented on HDFS-4794:
--------------------------------------------
I see that JspHelper.namenodeAddr is being used only in following jsp's:
1) browseBlock.jsp
2) browseDirectory.jsp
3) tail.jsp
In all these cases it seems fine to use namenode rpc-address.
I am fine with this patch if you are sure that all these jsp's have been
sufficiently tested in your clusters. If you have a running cluster, it should
be possible to test these by clicking on various links in the web-ui.
> Browsing filesystem via webui throws kerberos exception when NN service RPC
> is enabled in a secure cluster
> ----------------------------------------------------------------------------------------------------------
>
> Key: HDFS-4794
> URL: https://issues.apache.org/jira/browse/HDFS-4794
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: security
> Affects Versions: 1.1.2
> Reporter: Benoy Antony
> Assignee: Benoy Antony
> Attachments: HDFS-4794.patch
>
>
> Browsing filesystem via webui throws kerberos exception when NN service RPC
> is enabled in a secure cluster
> To reproduce this error,
> Enable security
> Enable serviceRPC by setting dfs.namenode.servicerpc-address and use a
> different port than the rpc port.
> Click on "Browse the filesystem" on NameNode web.
> The following error will be shown :
> Call to NN001/12.123.123.01:8030 failed on local exception:
> java.io.IOException: javax.security.sasl.SaslException: GSS initiate failed
> [Caused by GSSException: No valid credentials provided (Mechanism level:
> Failed to find any Kerberos tgt)]
--
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
