You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@sentry.apache.org by "Sravya Tirukkovalur (JIRA)" <ji...@apache.org> on 2014/09/15 22:08:34 UTC

[jira] [Updated] (SENTRY-380) Clean up some grantorPrincipal semantics

     [ https://issues.apache.org/jira/browse/SENTRY-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sravya Tirukkovalur updated SENTRY-380:
---------------------------------------
    Attachment: SENTRY-380.0.patch

> Clean up some grantorPrincipal semantics
> ----------------------------------------
>
>                 Key: SENTRY-380
>                 URL: https://issues.apache.org/jira/browse/SENTRY-380
>             Project: Sentry
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Sravya Tirukkovalur
>            Assignee: Sravya Tirukkovalur
>             Fix For: 1.5.0
>
>         Attachments: SENTRY-380.0.patch
>
>
> Came from SENTRY-327 review:
> - I do not think grantorPrincipal is required for createRole, we should instead pass it for alterSentryRoleGrantPrivilege and alterSentryRoleRevokePrivilege?
> - As we pass grantorPrincipal as the user invoking the thrift request(requestorUserName), we may keep it consistent and avoid possibility of passing different requestorUserName and grantorPrincipal by getting rid of grantorPrincipal field in the TSentryPrivilege and TSentryRole?



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