[jira] [Assigned] (NIFI-7292) ListFile should apply filters before checking permissions.

["Simon Bence (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-7292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Bence reassigned NIFI-7292:
---------------------------------

    Assignee: Simon Bence

> ListFile should apply filters before checking permissions.
> ----------------------------------------------------------
>
>                 Key: NIFI-7292
>                 URL: https://issues.apache.org/jira/browse/NIFI-7292
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.9.2
>            Reporter: Matthew Clarke
>            Assignee: Simon Bence
>            Priority: Major
>
> I noticed that NiFi's ListFile processor (and probably other list based processors) will check permissions on sub-directories before it evaluates the path filter.   
> Let's assume we have a mounted directory (/NiFi/mount) that contains sub directories (A, B, C, D, and private).  The NiFi Service user has permissions to access all directories A,B,C, and D, but not the "private" directory.
> I then add a path filter in my ListFile to exclude the "private" directory 
> (for example:  (?!(private)).* )
> When I start the ListFile it errors because the NiFi service user does not have permissions to "private" directory even though I have no intention of listing anything from that directory.  Since it Errors it does not listed files from any directory including those which have the needed permissions.
> If I give the NiFi service user access to that "private" dir then the listing works ignoring the "private" dir files.
> I feel as though the processor should apply the path and/or file filters before checking permissions?
> Users may not have ability to edit permissions on some sub directories. And with other sub-directories having being dynamically created or having a very large number of sub-directories, creating a separate ListFile for each sub-directory is not a desirable solution either.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)