You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2012/05/02 20:34:49 UTC
[jira] [Commented] (HADOOP-8345) HttpServer adds SPNEGO filter
mapping but does not register the SPNEGO filter
[ https://issues.apache.org/jira/browse/HADOOP-8345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266796#comment-13266796 ]
Alejandro Abdelnur commented on HADOOP-8345:
--------------------------------------------
Also we we should probably revisit how the webui gets protected with SPENGO, which at the moment is documented as adding the AuthenticationFilterInitializer. If we already have the SPNEGO filter registered, it would be just matters of handling that in the code. This handling should be done with a switch as web UIs in many setups may not want to use SPNEGO as browsers are not configured to use Kerberos (instead they want to use the own custom intranet authentication)
> HttpServer adds SPNEGO filter mapping but does not register the SPNEGO filter
> -----------------------------------------------------------------------------
>
> Key: HADOOP-8345
> URL: https://issues.apache.org/jira/browse/HADOOP-8345
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 2.0.0
> Reporter: Alejandro Abdelnur
> Priority: Critical
> Fix For: 2.0.0
>
>
> It seems the mapping was added to fullfil HDFS requirements, where the SPNEGO filter is registered.
> The registration o the SPNEGO filter should be done at common level instead to it is avail for all components using HttpServer if security is ON.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira