From dev-return-24949-archive-asf-public=cust-asf.ponee.io@atlas.apache.org Mon Jul 9 15:27: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 918A6180676 for ; Mon, 9 Jul 2018 15:27:03 +0200 (CEST) Received: (qmail 27615 invoked by uid 500); 9 Jul 2018 13:27:02 -0000 Mailing-List: contact dev-help@atlas.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@atlas.apache.org Delivered-To: mailing list dev@atlas.apache.org Received: (qmail 27335 invoked by uid 99); 9 Jul 2018 13:27: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; Mon, 09 Jul 2018 13:27: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 18CAE1A10D0 for ; Mon, 9 Jul 2018 13:27:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, 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 FsIr_rZrBLQ3 for ; Mon, 9 Jul 2018 13:27: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 BDCCA5F1BD for ; Mon, 9 Jul 2018 13:27:00 +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 53B04E0056 for ; Mon, 9 Jul 2018 13:27: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 11A3421EEA for ; Mon, 9 Jul 2018 13:27:00 +0000 (UTC) Date: Mon, 9 Jul 2018 13:27:00 +0000 (UTC) From: "Alberto Romero (JIRA)" To: dev@atlas.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ATLAS-2784) Wildcards not supported for authorization granularity in Ranger policies 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/ATLAS-2784?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Alberto Romero updated ATLAS-2784: ---------------------------------- Description:=20 Creating Ranger policies for Atlas resources (such as entities, types, term= s, taxonomies) does not allow for actual multitenancy or segregation of per= missions due to policies ignoring wildcards (*). For example, cannot define= a policy for type "user_*" to allow users or groups of users to create, re= ad or update only types that start with the string "user_". The problem is that Atlas throws a 403 error "You are not authorized for RE= AD on [ENTITY] : *=C2=A0*"* even when trying to read a specific entity that= would match the pattern that contains the wildcard. In the UI is exactly t= he same. The expected behaviour would be for the user to only be able to se= e entities, terms, etc that match the pattern but the fact is that it compl= ains about not having being able to READ on [ENTITY] : *. The ***=C2=A0in e= rror is the clue there, it is actually expecting access to everything. It is only when we add the users to a policy that gives them access to '*'= that it works for them. was: Creating Ranger policies for Atlas resources (such as entities, types, term= s, taxonomies) does not allow for actual multitenancy or segregation of per= missions due to policies ignoring wildcards (*). For example, cannot define= a policy for type "user_*" to allow users or groups of users to create, re= ad or update only types that start with the string "user_". The problem is that Atlas throws a 403 error "You are not authorized for RE= AD on [ENTITY] : *" even when trying to read a specific entity that would m= atch the pattern that contains the wildcard. In the UI is exactly the same.= The expected behaviour would be for the user to only be able to see entiti= es, terms, etc that match the pattern but the fact is that it complains abo= ut not having being able to READ on [ENTITY] : *. The '*' in error is the c= lue there, it is actually expecting access to everything. It is only when we add the users to a policy that gives them access to '*' = that it works for them. > Wildcards not supported for authorization granularity in Ranger policies > ------------------------------------------------------------------------ > > Key: ATLAS-2784 > URL: https://issues.apache.org/jira/browse/ATLAS-2784 > Project: Atlas > Issue Type: Improvement > Components: atlas-core > Affects Versions: 0.8.2 > Reporter: Alberto Romero > Priority: Major > > Creating Ranger policies for Atlas resources (such as entities, types, te= rms, taxonomies) does not allow for actual multitenancy or segregation of p= ermissions due to policies ignoring wildcards (*). For example, cannot defi= ne a policy for type "user_*" to allow users or groups of users to create, = read or update only types that start with the string "user_". > The problem is that Atlas throws a 403 error "You are not authorized for = READ on [ENTITY] : *=C2=A0*"* even when trying to read a specific entity th= at would match the pattern that contains the wildcard. In the UI is exactly= the same. The expected behaviour would be for the user to only be able to = see entities, terms, etc that match the pattern but the fact is that it com= plains about not having being able to READ on [ENTITY] : *. The ***=C2=A0in= error is the clue there, it is actually expecting access to everything. > It is only when we add the users to a policy that gives them access to '= *' that it works for them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)