[
https://issues.apache.org/jira/browse/HADOOP-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035808#comment-13035808
]
Todd Lipcon commented on HADOOP-6832:
-------------------------------------
bq. incorporated todd's suggestions, although i'm not wild about doing the
username lookup for each request.
What do you mean by "username lookup" here? The conf lookup only happens when
the HttpServer starts. The "new User()" construction does happen for every
request, but that's hardly heavy lifting (eg we do the same thing on every RPC)
bq. The default user is already in the code and doesn't need to be in the
configuration file too.
The same could be said for every other default throughout all of common, HDFS,
and MR, no? This is our status quo.
bq. Using a non-unix userid means the chance for false positives is much lower.
Besides, dr. who is fun.
Apparently most of our very-confused customers who've filed tickets about this
don't agree. To quote one operator:
{noformat}
One thing I'd like to add is the fact that DrWho.Tardis are the default
user.group for Hadoop is horrible and confusing. For my $0.02 on this as
a sys-admin I want a useful error message that doesn't make me go digging
though the Hadoop Jira for 15 minutes
{noformat}
> Provide a web server plugin that uses a static user for the web UI
> ------------------------------------------------------------------
>
> Key: HADOOP-6832
> URL: https://issues.apache.org/jira/browse/HADOOP-6832
> Project: Hadoop Common
> Issue Type: New Feature
> Components: security
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Attachments: h-6382.patch, h-6832.patch, h-6832.patch, h-6832.patch,
> hadoop-6832.txt, static-web-user.patch
>
>
> We need a simple plugin that uses a static user for clusters with security
> that don't want to authenticate users on the web UI.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
