[
https://issues.apache.org/jira/browse/NIFI-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15275354#comment-15275354
]
ASF GitHub Bot commented on NIFI-1858:
--------------------------------------
Github user joewitt commented on the pull request:
https://github.com/apache/nifi/pull/419#issuecomment-217663105
It is expected. The ReportingTask isn't acting on behalf of the user that
started it. It is acting on behalf of NiFi itself and so does have access.
This sort of 'authorization gap' is no different than a DFM that cannot click
on a particular piece of content for instance and yet they could redirect the
live dataflow. Probably makes sense to think of it as someone with DFM access
having both DFM and Provenance access.
> Add ReportingTask for sending provenance events over Site-To-Site
> -----------------------------------------------------------------
>
> Key: NIFI-1858
> URL: https://issues.apache.org/jira/browse/NIFI-1858
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
> Fix For: 0.7.0
>
>
> Currently if someone wants to export Provenance events they can do so through
> a ReportingTask. Rather than creating specialized ReportingTasks for
> different destinations, another approach would be to send provenance events
> to another NiFi instance over site-to-site and then use the standard
> processors in that other instance to store the events in the desired
> destination.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
