Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D5DC9200C5C for ; Thu, 20 Apr 2017 13:44:18 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D46F4160B9F; Thu, 20 Apr 2017 11:44:18 +0000 (UTC) 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 275C5160B91 for ; Thu, 20 Apr 2017 13:44:18 +0200 (CEST) Received: (qmail 89050 invoked by uid 500); 20 Apr 2017 11:44:17 -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 89041 invoked by uid 99); 20 Apr 2017 11:44:17 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Apr 2017 11:44:17 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 05982C2109 for ; Thu, 20 Apr 2017 11:44:17 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id m-OCzq0OEnir for ; Thu, 20 Apr 2017 11:44:16 +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 186BB5F39D for ; Thu, 20 Apr 2017 11:44:11 +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 2D81CE0D56 for ; Thu, 20 Apr 2017 11:44:05 +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 5DF5F21B5E for ; Thu, 20 Apr 2017 11:44:04 +0000 (UTC) Date: Thu, 20 Apr 2017 11:44:04 +0000 (UTC) From: =?utf-8?Q?Oliv=C3=A9r_Szab=C3=B3_=28JIRA=29?= To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-20768) Local Ambari user with no cluster role must not be able to access Logsearch UI MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 20 Apr 2017 11:44:19 -0000 [ https://issues.apache.org/jira/browse/AMBARI-20768?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliv=C3=A9r Szab=C3=B3 updated AMBARI-20768: ---------------------------------- Fix Version/s: 2.5.1 > Local Ambari user with no cluster role must not be able to access Logsear= ch UI > -------------------------------------------------------------------------= ----- > > Key: AMBARI-20768 > URL: https://issues.apache.org/jira/browse/AMBARI-20768 > Project: Ambari > Issue Type: Bug > Components: logsearch > Affects Versions: trunk, 2.5.0 > Reporter: Keta Patel > Assignee: Keta Patel > Fix For: 2.5.1 > > Attachments: all_tests_successful.png, AMBARI-20768_branch-2.5.0.= patch, AMBARI-20768_branch-2.5_updated.patch > > > A local Ambari user with no cluster roles assigned to it can successfully= log into the Logsearch UI. > Logsearch service exercises restriction on who can access its UI using a = property "logsearch.roles.allowed". This property is a comma-separated list= of roles to be allowed access to Logsearch UI. This defect deals with the = following issue: > 1. If Logsearch service requires that only certain roles be allowed to ac= cess its UI, then a local Ambari user with no roles must not be allowed to = access the UI. > DESIRED BEHAVIOR: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 1. A local user with no role assigned to it, must not be able to access L= ogsearch UI. > Note: The description has been updated by removing the aspect of correcti= ng the behavior for Ambari Administrator role for the Logsearch UI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)