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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
