sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dapeng Sun (JIRA)" <>
Subject [jira] [Commented] (SENTRY-498) Sentry authorization V2 via Hive authorization framework
Date Wed, 03 Jun 2015 02:34:49 GMT


Dapeng Sun commented on SENTRY-498:

Hi [~Huang Xiaomeng], are you still working on this ticket? If not, do you think it is possible
for me and Colin take over this jira and its subtasks?

> Sentry authorization V2 via Hive authorization framework
> --------------------------------------------------------
>                 Key: SENTRY-498
>                 URL:
>             Project: Sentry
>          Issue Type: New Feature
>            Reporter: Xiaomeng Huang
>            Assignee: Xiaomeng Huang
>         Attachments: SENTRY-498.003.patch
> Currently Sentry grant/revoke privileges via hook DDLTask, and do authorization via HiveSemanticAnalyzerHook.
Now hive has a pluggable authorization framework via exposing some interfaces HiveAccessController
and HiveAuthorizationValidator. HiveAccessController is used to grant/revoke roles and privileges.
HiveAuthorizationValidator is used to do fine-grained authorization. 
> Advantages to use this framework to grant/revoke privileges and do authorization:
> - This framework is very convenient to use by external authorization system. 
> - Using this framework will be better accepted by community.
> - We don't need to take efforts to add so many hooks. 
> - Some hooks has limitations. e.g. For column level security, we can't get accessed cloumns
from query via HiveSemanticAnalyzerHook, so I extend the readEntity to put accessed columns
into it(HIVE-7730). But if we use this framework, we don't need to extend the readEntity,
we can just get accessed columns from ColumnAccessInfo directly. 
> I will not remove the old sentry authorization framework, I will just add a new authorizationV2
via implement Hive authorization framework. If all the e2e tests passed, we can mark the old
authorization deprecated.

This message was sent by Atlassian JIRA

View raw message