You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2018/12/18 18:34:00 UTC

[jira] [Commented] (SENTRY-2481) Filter HMS server-side objects based on HMS user authorization

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

Hadoop QA commented on SENTRY-2481:
-----------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12952219/SENTRY-2481.1.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/4298/console

This message is automatically generated.

> Filter HMS server-side objects based on HMS user authorization
> --------------------------------------------------------------
>
>                 Key: SENTRY-2481
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2481
>             Project: Sentry
>          Issue Type: New Feature
>          Components: Sentry
>            Reporter: Sergio Peña
>            Assignee: Sergio Peña
>            Priority: Major
>         Attachments: SENTRY-2481.1.patch
>
>
> Sentry provides a mechanism to filter HMS objects from users who are not authorized to view certain objects, but this filter happens on the HMS client only. The support for the HMS server-side is needed as there might clients who access the server using Thrift API causing this security concern.
>  
> To provide with such support. Sentry should re-use the SentryMetaStoreFilterHook, which will be called by the HMS server, in order to filter the unwanted objects.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)