[
https://issues.apache.org/jira/browse/NIFI-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388174#comment-15388174
]
ASF GitHub Bot commented on NIFI-1950:
--------------------------------------
GitHub user bbende opened a pull request:
https://github.com/apache/nifi/pull/702
NIFI-1950 Updating FileAuthorizer to convert access controls from inp…
…ut and output ports during legacy conversion
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bbende/nifi NIFI-1950
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/702.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 #702
----
commit ded2830ccca8d9377bf8f5f52ce5c9a4a6040b96
Author: Bryan Bende <[email protected]>
Date: 2016-07-21T16:18:09Z
NIFI-1950 Updating FileAuthorizer to convert access controls from input and
output ports during legacy conversion
----
> Convert 0.x site-to-site access policies when possible
> ------------------------------------------------------
>
> Key: NIFI-1950
> URL: https://issues.apache.org/jira/browse/NIFI-1950
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core Framework
> Reporter: Matt Gilman
> Assignee: Bryan Bende
> Priority: Blocker
> Fix For: 1.0.0
>
>
> In the 0.x baseline access a Remote Port is configurable. These
> authorizations are stored in the flow.xml. In the 1.0.0 baseline these
> decisions will be made by a configurable authorizer. When possible, these
> access policies need to be converted to the authorizer upon starting with a
> legacy flow.
> Note: This won't be possible when the authorizer is externally managed. When
> this is the case, we'll need to document that the access policies will need
> to be manually restored using the external tool the authorizer supports.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
