[
https://issues.apache.org/jira/browse/NIFIREG-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16550309#comment-16550309
]
ASF GitHub Bot commented on NIFIREG-186:
----------------------------------------
GitHub user ijokarumawak opened a pull request:
https://github.com/apache/nifi-registry/pull/131
NIFIREG-186: Adding Ranger authorizer
- Renger Authorizer is deployed as Registry extension.
- Added /config REST endpoint to expose Registry configuration for UI to
determine if user, group and policies can be edited.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ijokarumawak/nifi-registry nifireg-186
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi-registry/pull/131.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 #131
----
commit 11e4734558f51f7391e0e7f4c4d75b49574f8bb7
Author: Koji Kawamura <ijokarumawak@...>
Date: 2018-06-27T01:45:34Z
NIFIREG-186: Adding Ranger authorizer
- Renger Authorizer is deployed as Registry extension.
- Added /config REST endpoint to expose Registry configuration for UI to
determine if user, group and policies can be edited.
----
> Create Authorizer implementation that uses Apache Ranger
> --------------------------------------------------------
>
> Key: NIFIREG-186
> URL: https://issues.apache.org/jira/browse/NIFIREG-186
> Project: NiFi Registry
> Issue Type: Improvement
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
> Priority: Major
>
> In addition to the standard file-based Authorizer, we should provide an
> Authorizer implementation that uses Apache Ranger, so that users implement
> centralized authorization against both NiFi and NiFi Registry.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
