You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/04/13 20:36:42 UTC

[jira] [Commented] (NIFI-3706) FileAuthorizer - Grants permissions to non-existent policy

    [ https://issues.apache.org/jira/browse/NIFI-3706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968174#comment-15968174 ] 

ASF GitHub Bot commented on NIFI-3706:
--------------------------------------

GitHub user mcgilman opened a pull request:

    https://github.com/apache/nifi/pull/1673

    NIFI-3706: Removing non-existent resource when converting a legacy authorized users file

    - Removing non-existent resource when converting a legacy authorized users file.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mcgilman/nifi NIFI-3706

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1673.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1673
    
----
commit 38f6f619ded6b833d88c52d0215817450e6901c1
Author: Matt Gilman <ma...@gmail.com>
Date:   2017-04-13T20:14:45Z

    NIFI-3706:
    - Removing non-existent resource when converting a legacy authorized users file.

----


> FileAuthorizer - Grants permissions to non-existent policy
> ----------------------------------------------------------
>
>                 Key: NIFI-3706
>                 URL: https://issues.apache.org/jira/browse/NIFI-3706
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Matt Gilman
>            Priority: Trivial
>             Fix For: 1.2.0
>
>
> When considering a legacy authorized users file, the FileAuthorizer grants permission to WRITE site-to-site. These policy does not exist and is consequently never evaluated. We should be able to remove it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)