sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sravya Tirukkovalur (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SENTRY-380) Clean up some grantorPrincipal semantics
Date Mon, 15 Sep 2014 21:33:34 GMT

     [ 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.1.patch

Attaching a patch, which basically cleans up the use of grantorPrincipal in creating roles/groups.
Created a follow on jira to update the jdo and the models to store grantorPrincipal as part
of the mapping: SENTRY-440.


> 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, SENTRY-380.1.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)

Mime
View raw message