sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SENTRY-750) Use the Sqoop Server principal as the requester when removing the Sqoop resource
Date Tue, 02 Jun 2015 13:30:18 GMT

    [ https://issues.apache.org/jira/browse/SENTRY-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569094#comment-14569094
] 

Hadoop QA commented on SENTRY-750:
----------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12736815/SENTRY-750.001.patch against master.

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/615/console

This message is automatically generated.

> Use the Sqoop Server principal as the requester when removing the Sqoop resource
> --------------------------------------------------------------------------------
>
>                 Key: SENTRY-750
>                 URL: https://issues.apache.org/jira/browse/SENTRY-750
>             Project: Sentry
>          Issue Type: Bug
>    Affects Versions: 1.6.0
>            Reporter: guoquan
>            Assignee: guoquan
>         Attachments: SENTRY-750.001.patch
>
>
> When the user1 is the owner of job1, the user1 can delete job1. The Sqoop Server receives
the user1's request for deleting job1. It will check the job1's owner, if the owner equals
user1, the Sqoop server will not do the authorizaiton check. When the repository delete the
job1, the Sqoop server will send a request to Sentry service for removing the privileges related
the job1. The Sqoop Server should send the server principal as the requestor to Sentry Service
not the user1. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message