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 202A7200C36 for ; Thu, 23 Feb 2017 13:05:52 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1EDDE160B50; Thu, 23 Feb 2017 12:05:52 +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 5FE18160B62 for ; Thu, 23 Feb 2017 13:05:51 +0100 (CET) Received: (qmail 43803 invoked by uid 500); 23 Feb 2017 12:05:50 -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 43788 invoked by uid 99); 23 Feb 2017 12:05:50 -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; Thu, 23 Feb 2017 12:05:50 +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 1F00A1A07CE for ; Thu, 23 Feb 2017 12:05:50 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] 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 FFk152hR57AF for ; Thu, 23 Feb 2017 12:05:49 +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 254135FE25 for ; Thu, 23 Feb 2017 12:05:49 +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 5960BE08F4 for ; Thu, 23 Feb 2017 12:05:45 +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 4E4192413A for ; Thu, 23 Feb 2017 12:05:44 +0000 (UTC) Date: Thu, 23 Feb 2017 12:05:44 +0000 (UTC) From: "M Madhan Mohan Reddy (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-20050) Issue while importing workflow with insufficient permissions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 23 Feb 2017 12:05:52 -0000 [ https://issues.apache.org/jira/browse/AMBARI-20050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] M Madhan Mohan Reddy updated AMBARI-20050: ------------------------------------------ Attachment: AMBARI-20050_trunk.patch > Issue while importing workflow with insufficient permissions > ------------------------------------------------------------ > > Key: AMBARI-20050 > URL: https://issues.apache.org/jira/browse/AMBARI-20050 > Project: Ambari > Issue Type: Bug > Components: ambari-views > Affects Versions: 2.5.0 > Reporter: Supreeth Sharma > Assignee: M Madhan Mohan Reddy > Priority: Critical > Fix For: 2.5.0 > > Attachments: AMBARI-20050_trunk.patch > > > Facing Issue while importing workflow with insufficient permissions. Though /api/v1/views/WORKFLOW_MANAGER/versions/1.0.0/instances/WFM/resources/proxy/readWorkflowDetail?workflowXmlPath=/user/admin/new/email.xml is failed with 500 code, its not been handled on the UI. > UI is stuck in import phase. > Steps to reproduce : > 1) Login as user1 and submit workflow and save to hdfs location /user/user1 > 2) Now login as user2 who doesn't have access to /user/user1 . > Now user2 can view the workflow status in the dashboard. > 3) Click on edit workflow and try to navigate to designer page. > 4) Due to lack of permission, user is not allowed to import the workflow and UI is not handling this error. > This should be properly handled on the UI and appropriate error message need to be displayed. -- This message was sent by Atlassian JIRA (v6.3.15#6346)