You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Koji Kawamura (JIRA)" <ji...@apache.org> on 2018/08/07 06:56:00 UTC
[jira] [Comment Edited] (RANGER-2157) Add NiFi Registry service
definition and NiFiRegistryClient
[ https://issues.apache.org/jira/browse/RANGER-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16550346#comment-16550346 ]
Koji Kawamura edited comment on RANGER-2157 at 8/7/18 6:55 AM:
---------------------------------------------------------------
Attaching the first pass of a patch for NiFi Registry service def and resource lookup.
In order to test this against a real NiFi Registry instance, you can do the following:
Build this branch with "mvn clean install -Pinclude-ranger"
https://github.com/ijokarumawak/nifi-registry/tree/nifireg-186
The NiFi Registry distribution will be in nifi-registry-assembly/target, copy the tar.gz somewhere and extract it.
Refer [NiFi Registry Ranger extension README.md|https://github.com/apache/nifi-registry/blob/29239be99a5f6275060ecbdcb16ae9a8e7abef86/nifi-registry-extensions/nifi-registry-ranger-extension/README.md] for configuration details.
In order for NiFi Registry to perform authorization, it needs to be secured, this is done by configuring conf/nifi-registry.properties to use HTTPS. Also, conf/authorizers.xml should be configured to use RangerAuthorizer. Example configurations are available here:
https://github.com/ijokarumawak/nifi-registry-ranger/tree/master/nifi-registry/conf
To start NiFi Registry, execute 'bin/nifi-registry.sh start'.
Navigate to https://localhost:18443/nifi-registry
You will need a client certificate loaded in your browser to authenticate, or configure NiFi Registry to use LDAP.
was (Author: ijokarumawak):
Attaching the first pass of a patch for NiFi Registry service def and resource lookup.
In order to test this against a real NiFi Registry instance, you can do the following:
Build this branch with "mvn clean install"
https://github.com/ijokarumawak/nifi-registry/tree/nifireg-186
The NiFi Registry distribution will be in nifi-registry-assembly/target, copy the tar.gz somewhere and extract it.
Also, you will need to build the ranger plug-in at NiFi Registry side by:
{code}
mvn -f nifi-registry-ranger install
mkdir -p ${NIFI_REG_HOME}/ranger/lib/
cp -rp nifi-registry-ranger/target/lib/* ${NIFI_REG_HOME}/ranger/lib/
{code}
In order for NiFi Registry to perform authorization, it needs to be secured, this is done by configuring conf/nifi-registry.properties to use HTTPS. Also, conf/authorizers.xml should be configured to use RangerAuthorizer. Example configurations are available here:
https://github.com/ijokarumawak/nifi-registry-ranger/tree/master/nifi-registry/conf
To start NiFi Registry, execute 'bin/nifi-registry.sh start'.
Navigate to https://localhost:18443/nifi-registry
You will need a client certificate loaded in your browser to authenticate, or configure NiFi Registry to use LDAP.
> Add NiFi Registry service definition and NiFiRegistryClient
> -----------------------------------------------------------
>
> Key: RANGER-2157
> URL: https://issues.apache.org/jira/browse/RANGER-2157
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
> Priority: Major
> Attachments: 0001-RANGER-2157-Added-NiFi-Registry-service.patch
>
>
> Apache NiFi Registry is a subproject of Apache NiFi. NiFi Registry can manage versioned flow definitions so that NiFi users can version control their flows.
> Ranger already has NiFi service. This JIRA adds similar integration with NiFi Registry.
> The NiFi Registry integration will be split into two parts...
> The first part will be the service definition and the NiFiRegistryClient to perform resource look ups against NiFi Registry. This work will be tracked with this ticket.
> The second part is the plugin that will run in NiFi Registry and this part will live in the NiFi Registry codebase and is being tracked with this JIRA: NIFIREG-186
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)