[
https://issues.apache.org/jira/browse/NIFI-4255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16117831#comment-16117831
]
ASF GitHub Bot commented on NIFI-4255:
--------------------------------------
GitHub user YolandaMDavis opened a pull request:
https://github.com/apache/nifi/pull/2065
NIFI-4255 - added flag to allow migration of existing (source) acls
Testing Recommendations:
Using a secured Zookeeper instance with predefined paths/znodes use the ZK
Migrator to first export a json file containing nodes information. Then that
json file can be edited to alter or add acls to existing paths. The file can
then be reapplied to the source ZK server using the following example command:
`./zk-migrator.sh -s -z <zookeeper-server>:2181/nifi -f
<zk-node-acl-json-file> -k <client-jaas-file> --ignore-source
--use-existing-acl`
Confirm that acls are applied as expected using the zkCli.sh (or some other
ZK Client tool)
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [ x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA
number you are trying to resolve? Pay particular attention to the hyphen "-"
character.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [x] Is your initial contribution a single, squashed commit?
### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn
-Pcontrib-check clean install at the root nifi folder?
- [x] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file, including the main
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [x] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/YolandaMDavis/nifi NIFI-4255
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/2065.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 #2065
----
commit d4f4c78d669d6d2ab30692af15de7606191da545
Author: Yolanda M. Davis <yolanda.m.da...@gmail.com>
Date: 2017-08-08T04:03:42Z
NIFI-4255 - added flag to allow migration of existing (source) acls to
destination
NIFI-4255 - update to documentation
----
> Add support for providing ACLs for paths in Zookeeper Migration tool
> --------------------------------------------------------------------
>
> Key: NIFI-4255
> URL: https://issues.apache.org/jira/browse/NIFI-4255
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Tools and Build
> Affects Versions: 1.3.0
> Reporter: Yolanda M. Davis
> Assignee: Yolanda M. Davis
>
> Currently in the Zookeeper migration utility there is support for applying
> acls when importing zookeeper data (Znodes). However this support only
> applies default ACLs values (either Open or Creator specific), and the value
> used depends on if security is enabled or disabled in the destination
> Zookeeper instance. This may become problematic if the user/identity used to
> import zookeeper data does not align with the users/identities that require
> read/modify rights on the imported Znodes. This also doesn't provide users
> flexibility in defining specific rights or applying additional authorizations
> on paths.
> Enhancing the existing utility to support providing ACL information would
> offer users more flexibility in defining permissions and authentication
> schemes on znodes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
