[
https://issues.apache.org/jira/browse/HDFS-5796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345808#comment-14345808
]
Arun Suresh commented on HDFS-5796:
-----------------------------------
[~aw],
bq. .. One configures it in core-site.xml to enable it.
Aah.. apologize for the misunderstanding.. Am aware of us being able to
configure it via *hadoop.http.authentication.type* parameter in core-site.xml.
But like you mentioned, the user has to provide a jar containing the subclass
of {{AltKerberosAuthenticationHandler}}. I was just attempting to provider a
default implementation.
If you feel we should allow the user to configure a subclass.. then yes...
maybe we should close this JIRA and fix the actual problem, which I believe is
the multitude of filters
> The file system browser in the namenode UI requires SPNEGO.
> -----------------------------------------------------------
>
> Key: HDFS-5796
> URL: https://issues.apache.org/jira/browse/HDFS-5796
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.5.0
> Reporter: Kihwal Lee
> Assignee: Arun Suresh
> Priority: Blocker
> Attachments: HDFS-5796.1.patch, HDFS-5796.1.patch, HDFS-5796.2.patch,
> HDFS-5796.3.patch, HDFS-5796.3.patch
>
>
> After HDFS-5382, the browser makes webhdfs REST calls directly, requiring
> SPNEGO to work between user's browser and namenode. This won't work if the
> cluster's security infrastructure is isolated from the regular network.
> Moreover, SPNEGO is not supposed to be required for user-facing web pages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
