You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Bharat Viswanadham (JIRA)" <ji...@apache.org> on 2019/03/26 16:06:00 UTC
[jira] [Comment Edited] (HDDS-939) Add S3 access check to Ozone
manager
[ https://issues.apache.org/jira/browse/HDDS-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801873#comment-16801873 ]
Bharat Viswanadham edited comment on HDDS-939 at 3/26/19 4:05 PM:
------------------------------------------------------------------
Thank You [~ajayydv] for the contribution.
I have committed this to the trunk and ozone-0.4 branch.
was (Author: bharatviswa):
Thank You [~ajayydv] for the contribution.
I have committed this to trunk.
> Add S3 access check to Ozone manager
> ------------------------------------
>
> Key: HDDS-939
> URL: https://issues.apache.org/jira/browse/HDDS-939
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Manager, S3
> Reporter: Anu Engineer
> Assignee: Ajay Kumar
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 0.4.0, 0.5.0
>
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> Add the mapping from S3 User Identity to UGI inside Ozone Manager. Also add the access check permission, that is call into the checkAccess, which will be intercepted by Ranger or Ozone access check.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org