Mailing-List: contact issues-help@nifi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@nifi.apache.org
Date: Tue, 13 Sep 2016 17:34:20 +0000 (UTC)
From: "Matthew Clarke (JIRA)" <jira@apache.org>
To: issues@nifi.apache.org
Message-ID: <JIRA.13004663.1473787996000.561560.1473788060452@Atlassian.JIRA>
In-Reply-To: <JIRA.13004663.1473787996000@Atlassian.JIRA>
References: <JIRA.13004663.1473787996000@Atlassian.JIRA> <JIRA.13004663.1473787996449@arcas>
Subject: [jira] [Created] (NIFI-2769) Unable to view Component ID of
 "unknown" components in a provenance lineage graph.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 13 Sep 2016 17:34:22 -0000

Matthew Clarke created NIFI-2769:
------------------------------------

             Summary: Unable to view Component ID of "unknown" components in a provenance lineage graph.
                 Key: NIFI-2769
                 URL: https://issues.apache.org/jira/browse/NIFI-2769
             Project: Apache NiFi
          Issue Type: Improvement
          Components: Core Framework
    Affects Versions: 1.0.0
            Reporter: Matthew Clarke
            Priority: Minor


NiFi lineage that includes unknown components does not provide the minimum level of information needed to troubleshoot a dataflow in a secured NiFi user level component access policies.  Clicking on "view details" of an "unknown" component in a lineage graph returns an unauthorized response. User Should be able to at least retrieve the UUID for the unknown components.

An example use case:
A user (user M) has permissions to a process group with an input port.  That input port is fed by many different parent level connections from other components user M does not have permission to.  If user M performs a lineage search against a single FlowFile, it is not possible for user M to determine which of source connections the data came from.  This makes troubleshooting difficult as user must query all source dataflow users to do queries to see if they were the source of the data. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)