[
https://issues.apache.org/jira/browse/HADOOP-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683878#action_12683878
]
Hemanth Yamijala commented on HADOOP-5485:
------------------------------------------
There are two approaches I can think of.
In the short term, I think webinterface.private.actions should be checked and
actions disabled in the web page. This is what the standard Hadoop JSPs do.
In the longer term, we may want to unify the UI as per HADOOP-4712.
Matei, the admin changes to job priorities via command line can be controlled
by setting up ACLs, and is the way we are using here.
> Authorisation machanism required for acceesing jobtracker url :-
> jobtracker.com:port/scheduler
> ----------------------------------------------------------------------------------------------
>
> Key: HADOOP-5485
> URL: https://issues.apache.org/jira/browse/HADOOP-5485
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/fair-share
> Affects Versions: 0.20.0
> Reporter: Aroop Maliakkal
>
> FS scheduler should have some mechanism to authorize people who can access
> the advanced scheduler url http://jobtracker.com:port/scheduler . In large
> clusters , which has hundreds of users, any user can access the url now and
> change the priority of his/her runing job. We don't want the users to change
> the job priority. So we should restrcit users accessing the link and only
> admins should have access to the link.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
