From dev-return-17683-archive-asf-public=cust-asf.ponee.io@ranger.apache.org Wed Apr 11 23:57:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id D10C818067B for ; Wed, 11 Apr 2018 23:57:03 +0200 (CEST) Received: (qmail 17191 invoked by uid 500); 11 Apr 2018 21:57:03 -0000 Mailing-List: contact dev-help@ranger.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ranger.apache.org Delivered-To: mailing list dev@ranger.apache.org Received: (qmail 17179 invoked by uid 99); 11 Apr 2018 21:57:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Apr 2018 21:57:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 70B491A16BF for ; Wed, 11 Apr 2018 21:57:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -101.511 X-Spam-Level: X-Spam-Status: No, score=-101.511 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id z0po56QbLrII for ; Wed, 11 Apr 2018 21:57:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 3D9CC5FBC5 for ; Wed, 11 Apr 2018 21:57:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id BC801E0BD2 for ; Wed, 11 Apr 2018 21:57:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 38C2C241C8 for ; Wed, 11 Apr 2018 21:57:00 +0000 (UTC) Date: Wed, 11 Apr 2018 21:57:00 +0000 (UTC) From: "Abhay Kulkarni (JIRA)" To: dev@ranger.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (RANGER-2066) Hbase column family access is authorized by a tagged column in the column family MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/RANGER-2066?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhay Kulkarni updated RANGER-2066: ----------------------------------- Description:=20 ERROR=C2=A0SCENARIO: Table emp has 2 column families: personal_data(name,SSN,age) ; prof_data(ro= le, manager) Column emp/prof_data/role is tagged with OFFICIAL tag. Create following policies: Resource policy allows Read on table=3D*,=C2=A0**=C2=A0column-family=3D*,c= olumn=3D*=C2=A0 and Tag policy allows Read on OFFICIAL tag for a test_user. When test_user executes 'scan emp' command, two audit log records are creat= ed: 1. Resource: emp/personal_data Name / Type: column-family Allowed Policy allowing: Resource based policy 2. Resource: emp/prof_data Name / Type: column-family Allowed Policy allowing: TAG based policy for OFFICIAL tag prof_data column-family should not be authorized by a tagged role column in= it.=C2=A0 was: ERROR=C2=A0SCENARIO: Table emp has 2 col-families: personal_data(name,SSN,age) ; prof_data(role,= manager) Column emp/prof_data/role is tagged with OFFICIAL tag. Create following policies: Resource policy allows Read on table=3D*, column-family=3D*,column=3D*=C2= =A0 and Tag policy allows Read on OFFICIAL tag for a test_user. When test_user executes 'scan emp' command, two audit log records are creat= ed: 1. Resource: emp/personal_data Name / Type: column-family Allowed Policy allowing: Resource based policy 2. Resource: emp/prof_data Name / Type: column-family Allowed Policy allowing: TAG based policy for OFFICIAL tag prof_data column-family should not be authorized by a tagged role column in= it.=C2=A0 > Hbase column family access is authorized by a tagged column in the column= family > -------------------------------------------------------------------------= ------- > > Key: RANGER-2066 > URL: https://issues.apache.org/jira/browse/RANGER-2066 > Project: Ranger > Issue Type: Bug > Components: Ranger > Affects Versions: 1.0.0, master > Reporter: Anuja Leekha > Priority: Major > Fix For: master, 1.1.0 > > > ERROR=C2=A0SCENARIO: > Table emp has 2 column families: personal_data(name,SSN,age) ; prof_data(= role, manager) > Column emp/prof_data/role is tagged with OFFICIAL tag. > Create following policies: > Resource policy allows Read on table=3D*,=C2=A0**=C2=A0column-family=3D*= ,column=3D*=C2=A0 and Tag policy allows Read on OFFICIAL tag for a test_use= r. > When test_user executes 'scan emp' command, two audit log records are cre= ated: > 1. Resource: emp/personal_data > Name / Type: column-family > Allowed > Policy allowing: Resource based policy > 2. Resource: emp/prof_data > Name / Type: column-family > Allowed > Policy allowing: TAG based policy for OFFICIAL tag > prof_data column-family should not be authorized by a tagged role column = in it.=C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)