[
https://issues.apache.org/jira/browse/MAPREDUCE-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835123#action_12835123
]
Vinod K V commented on MAPREDUCE-1493:
--------------------------------------
Regarding putting the ACLs in JobHistory I've checked with [~jothipn] to see
how easy/difficult it is to put it in there. From what I understand from that
conversation, it is non-trivial to do it and will involve changes in our
JobHistory APIs and possibly in other places like Vaidya, Rumen which consume
JobHistory. Further, he was of the opinion that ACLs are simply a configuration
and may not exactly fit into the history file, though we agreed the line is
really blurred as to what should go into the history file and what should not.
Given that, I am leaning towards going with the conf file itself where the ACLs
are already present.
> Authorization for job-history pages
> -----------------------------------
>
> Key: MAPREDUCE-1493
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1493
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: jobtracker, security
> Reporter: Vinod K V
> Fix For: 0.22.0
>
>
> MAPREDUCE-1455 introduces authorization for most of the Map/Reduce jsp pages
> and servlets, but left history pages. This JIRA will make sure that
> authorization checks are made while accessing job-history pages also.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
