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 cust-asf.ponee.io (Postfix) with SMTP id E0056168449 for ; Wed, 9 Aug 2017 02:57:07 +0200 (CEST) Received: (qmail 69084 invoked by uid 500); 9 Aug 2017 00:57:07 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 69075 invoked by uid 99); 9 Aug 2017 00:57:07 -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, 09 Aug 2017 00:57:07 +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 947E71A0713 for ; Wed, 9 Aug 2017 00:57:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id j-hFAFQVyk9K for ; Wed, 9 Aug 2017 00:57:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 57EC85F613 for ; Wed, 9 Aug 2017 00:57:04 +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 79B91E0044 for ; Wed, 9 Aug 2017 00:57:03 +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 C783B21E14 for ; Wed, 9 Aug 2017 00:57:02 +0000 (UTC) Date: Wed, 9 Aug 2017 00:57:00 +0000 (UTC) From: "Amogh Patel (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-21687) User can't add node via Ambari UI when being part of both "cluster user" and "cluster admin" roles MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-21687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amogh Patel updated AMBARI-21687: --------------------------------- Description: User can't add node via Ambari UI when being part of both *cluster user* and *cluster administrator* roles. *Issue1:* The expected behavior of Ambari is to not allow same user/group to be part of 2 different roles and it WARNS that *Cannot save permissions.. Only 1 role allowed per user or group* but this can be fooled by creating two different groups and have a common user, which creates Issue2. *Issue2:* Due to above, user (part of cluster user and cluster admin) can't add node and Ambari UI goes in loop during node registration process and reloads the page again and again. Reproduced it with Ambari 2.5.1. Steps to reproduce: 1. Created group *foogroup* and user *foo1* and added it in *foogroup*. 2. Tried to add *foogroup* to roles cluster user and administrator and it doesn't allow with above warning. 3. Created a local user *test1* in Ambari. 4. Created 2 different group *clus_admin* and *cluster_user* and added *test1* in both of them. 5. Assigned *clus_admin* to cluster admin role and *clus_user* to cluster user role and was able to save and assign 2 different roles to same user. 6. Tried to add a new node with *test1* user and Ambari UI freaks out while registration and goes on loop. was: User can't add node via Ambari UI when being part of both "cluster user" and "cluster admin" roles. Issue1: The expected behavior of Ambari is to not allow same user/group to be part of 2 different roles and it WARNS that Cannot save permissions.. Only 1 role allowed per user or group but this can be fooled by creating two different groups and have a common user, which creates Issue2. Issue2: Due to above, user (part of cluster user and cluster admin) can't add node and Ambari UI goes in loop during node registration process and reloads the page again and again. Reproduced it with Ambari 2.5.1. Steps to reproduce: 1. Created group foogroup *and user *foo1 *and added it in foogroup*. 2. Tried to add* foogroup* to roles cluster user and administrator and it doesn't allow with above warning. 3. Created a local user test1 in Ambari. 4. Created 2 different group clus_admin and cluster_user and added test1 in both of them. 5. Assigned clus_admin to cluster admin role and *clus_user to cluster user role and was able to save and assign 2 differen*t roles to same user. 6. Tried to add a new node with* test1 *user and Ambari UI freaks out while registration and goes on loop. > User can't add node via Ambari UI when being part of both "cluster user" and "cluster admin" roles > -------------------------------------------------------------------------------------------------- > > Key: AMBARI-21687 > URL: https://issues.apache.org/jira/browse/AMBARI-21687 > Project: Ambari > Issue Type: Bug > Components: ambari-sever > Affects Versions: 2.5.1 > Reporter: Amogh Patel > > User can't add node via Ambari UI when being part of both *cluster user* and *cluster administrator* roles. > *Issue1:* The expected behavior of Ambari is to not allow same user/group to be part of 2 different roles and it WARNS that *Cannot save permissions.. Only 1 role allowed per user or group* but this can be fooled by creating two different groups and have a common user, which creates Issue2. > *Issue2:* Due to above, user (part of cluster user and cluster admin) can't add node and Ambari UI goes in loop during node registration process and reloads the page again and again. > Reproduced it with Ambari 2.5.1. Steps to reproduce: > 1. Created group *foogroup* and user *foo1* and added it in *foogroup*. > 2. Tried to add *foogroup* to roles cluster user and administrator and it doesn't allow with above warning. > 3. Created a local user *test1* in Ambari. > 4. Created 2 different group *clus_admin* and *cluster_user* and added *test1* in both of them. > 5. Assigned *clus_admin* to cluster admin role and *clus_user* to cluster user role and was able to save and assign 2 different roles to same user. > 6. Tried to add a new node with *test1* user and Ambari UI freaks out while registration and goes on loop. -- This message was sent by Atlassian JIRA (v6.4.14#64029)