Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/2973
I created a flow which uses 3 `GenerateFlowFile` processors (named
_Component A_, _Component A_, and _Component A (B)_) to evaluate the new
filtering behavior. Each generates a flowfile with the content and _source_
attribute indicating the source (for the 2nd processor, the message & attribute
refer to _Component A (2)_). I exercised the
`SiteToSiteProvenanceReportingTask` with no accept/deny list, then only an
accept value, then both. The functionality worked as expected; explicit deny
overrode allow (see screenshot).

The template is [available
here](https://gist.github.com/alopresto/b78ec5da5482f4af7f88faf7eeefd3b7).
---