[
https://issues.apache.org/jira/browse/NIFI-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377329#comment-16377329
]
Matt Gilman commented on NIFI-4907:
-----------------------------------
[~markbean]
Thanks for taking the time for writing up such a detailed synopsis. These
provenance query capabilities were designed in support of multi-tenant flow
management. In these multi-tenant environments, users only have access to a
small subset of the components in NiFi flow.
Returning placeholder events for unauthorized components was certainly
considered for query results. However, considering these multi-tenant
scenarios, returning placeholder events would make more work for the user to
filter through these or perform more complex searches. Since the results are
event centric, automatically filtering these out was the better approach. While
inconsistent with provenance queries, returning placeholder events did make
sense for lineage requests since those are lineage centric. The lineage is a
sequence of events that only makes sense as a whole.
'View the data' policies are used to enforce access to content and metadata.
This includes the actual data of the flowfile (content), the attributes of the
flowfile and details of the event (metadata). The details of the event include
bits about the event and the component that generated it including the
component name (processor, port, or connection) and type. While these component
specific bits are managed and controlled through 'view|modify the component'
policies, they are also part of the event data model and may be included in the
serialized event. Because they exist outside the context of the component that
generated it, those details are enforced through 'view the data' policy for
that component. In the future, if you have any concerns regarding security or
policy enforcement, please report them accordingly [1].
[1] https://nifi.apache.org/security.html
> Provenance authorization refactoring
> ------------------------------------
>
> Key: NIFI-4907
> URL: https://issues.apache.org/jira/browse/NIFI-4907
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.5.0
> Reporter: Mark Bean
> Priority: Major
>
> Currently, the 'view the data' component policy is too tightly coupled with
> Provenance queries. The 'query provenance' policy should be the only policy
> required for viewing Provenance query results. Both 'view the component' and
> 'view the data' policies should be used to refine the appropriate visibility
> of event details - but not the event itself.
> 1) Component Visibility
> The authorization of Provenance events is inconsistent with the behavior of
> the graph. For example, if a user does not have 'view the component' policy,
> the graph shows this component as a "black box" (no details such as name,
> UUID, etc.) However, when querying Provenance, this component will show up
> including the Component Type and the Component Name. This is in effect a
> violation of the policy. These component details should be obscured in the
> Provenance event displayed if user does not have the appropriate 'view the
> component' policy.
> 2) Data Visibility
> For a Provenance query, all events should be visible as long as the user
> performing the query belongs to the 'query provenance' global policy. As
> mentioned above, some information about the component may be obscured
> depending on 'view the component' policy, but the event itself should be
> visible. Additionally, details of the event (clicking the View Details "i"
> icon) should only be accessible if the user belongs to the 'view the data'
> policy for the affected component. If the user is not in the appropriate
> 'view the data' policy, a popup warning should be displayed indicating the
> reason details are not visible with more specific detail than the current
> "Contact the system administrator".
> 3) Lineage Graphs
> As with the Provenance table view recommendation above, the lineage graph
> should display all events. Currently, if the lineage graph includes an event
> belonging to a component which the user does not have 'view the data', it is
> shown on the graph as "UNKNOWN". As with Data Visibility mentioned above, the
> graph should indicate the event type as long as the user is in the 'view the
> component'. Subsequent "View Details" on the event should only be visible if
> the user is in the 'view the data' policy.
> In summary, for Provenance query results and lineage graphs, all events
> should be shown. Component Name and Component Type information should be
> conditionally visible depending on the corresponding component policy 'view
> the component' policy. Event details including Provenance event type and
> FlowFile information should be conditionally available depending on the
> corresponding component policy 'view the data'. Inability to display event
> details should provide feedback to the user indicating the reason.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
