[
https://issues.apache.org/jira/browse/MAPREDUCE-2858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126206#comment-13126206
]
Alejandro Abdelnur commented on MAPREDUCE-2858:
-----------------------------------------------
Robert,
Out of the box we can easily support Kerberos HTTP SPNEGO (via Alfredo), which
can use a domain cookie (and the domain could be of the grid).
If a company has concerns about domain cookies being stolen by any webserver
running in the domain, then domain cookies will not be allowed as browser will
just forward the cookie.s Certain measures can be done to alleviate this, such
as using a specific domain for your grid. This is where the security team of
the company has a saying on how to do things and what are policies that
applications must follow. As well as auditing the code before it goes into
production.
What I'm trying to say, we should try to solve a problem that is not our
problem, instead just provide hooks so it can be addressed on per user basis
according to their needs.
> MRv2 WebApp Security
> --------------------
>
> Key: MAPREDUCE-2858
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2858
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: applicationmaster, mrv2, security
> Affects Versions: 0.23.0
> Reporter: Luke Lu
> Assignee: Luke Lu
> Priority: Blocker
> Fix For: 0.23.0
>
>
> In MRv2, while the system servers (ResourceManager (RM), NodeManager (NM) and
> NameNode (NN)) run as "trusted"
> system users, the application masters (AM) run as users who submit the
> application. While this offers great flexibility
> to run multiple version of mapreduce frameworks (including their UI) on the
> same Hadoop cluster, it has significant
> implication for the security of webapps (Please do not discuss company
> specific vulnerabilities here).
> Requirements:
> # Secure authentication for AM (for app/job level ACLs).
> # Webapp security should be optional via site configuration.
> # Support existing pluggable single sign on mechanisms.
> # Should not require per app/user configuration for deployment.
> # Should not require special site-wide DNS configuration for deployment.
> This the top jira for webapp security. A design doc/notes of threat-modeling
> and counter measures will be posted on the wiki.
--
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
