[
https://issues.apache.org/jira/browse/HDDS-939?focusedWorklogId=217114&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-217114
]
ASF GitHub Bot logged work on HDDS-939:
---------------------------------------
Author: ASF GitHub Bot
Created on: 22/Mar/19 03:57
Start Date: 22/Mar/19 03:57
Worklog Time Spent: 10m
Work Description: bharatviswa504 commented on issue #634: HDDS-939. Add
S3 access check to Ozone manager. Contributed by Ajay Kumar.
URL: https://github.com/apache/hadoop/pull/634#issuecomment-475485998
> > I think if the awsAccessKey will not have realm, if it has just name we
shall not see the issue.
>
> That will not work, since there can be same user names in different
domains who are completely different users in real life.
Thank You @anuengineer for info.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 217114)
Time Spent: 50m (was: 40m)
> 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
> Time Spent: 50m
> 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: [email protected]
For additional commands, e-mail: [email protected]
