[
https://issues.apache.org/jira/browse/MAPREDUCE-7537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080217#comment-18080217
]
ASF GitHub Bot commented on MAPREDUCE-7537:
-------------------------------------------
riya2305 opened a new pull request, #8492:
URL: https://github.com/apache/hadoop/pull/8492
…-level security.
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
[MAPREDUCE-7523](https://issues.apache.org/jira/browse/MAPREDUCE-7523)
introduced mapreduce.security.denied-tasks: a single, global list of disallowed
class name prefixes applied to values of keys listed in
mapreduce.security.property-domain. By default the policy is not per-user or
per-group—the same rules apply to every submitter until an exception is
configured. mapreduce.security.allowed-users already provides a per-user bypass
of that deny list.
This work adds mapreduce.security.allowed-groups: a per-group bypass using
the submitter’s resolved group names from the cluster’s Hadoop group mapping
(UserGroupInformation.getGroupsSet() for that user).
### For code changes:
- [ ] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
### AI Tooling
If an AI tool was used:
- [ ] The PR includes the phrase "Contains content generated by <tool>"
where <tool> is the name of the AI tool used.
- [ ] My use of AI contributions follows the ASF legal policy
https://www.apache.org/legal/generative-tooling.html
> Hadoop MapReduce Task-Level Security - allowed Groups Bypass
> ------------------------------------------------------------
>
> Key: MAPREDUCE-7537
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7537
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: mrv2
> Reporter: Riya Khandelwal
> Priority: Major
>
> [MAPREDUCE-7523|https://issues.apache.org/jira/browse/MAPREDUCE-7523]
> introduced mapreduce.security.denied-tasks: a single, global list of
> disallowed class name prefixes applied to values of keys listed in
> mapreduce.security.property-domain. By default the policy is not per-user or
> per-group—the same rules apply to every submitter until an exception is
> configured. mapreduce.security.allowed-users already provides a per-user
> bypass of that deny list.
> This work adds mapreduce.security.allowed-groups: a per-group bypass using
> the submitter’s resolved group names from the cluster’s Hadoop group mapping
> (UserGroupInformation.getGroupsSet() for that user).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
