[
https://issues.apache.org/jira/browse/RANGER-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16150142#comment-16150142
]
Nikhil Purbhe commented on RANGER-1697:
---------------------------------------
Is it possible to leave any existing exclude policies in place (maybe in read
only form) until the user explicitly replaces it?
--> yes matt, we can mark the policies as disabled and it will act as read only
policy.but if user comes and mark it as enabled from UI then again that policy
will behave as exclude policy.
possible to automatically convert it into an equivalent 'include/normal' policy.
..>this way is also possible and those policies will act as include/normal
policy instead of exclude policy.
Request you to finalize the approach from above approaches.
> Update NiFi service def
> -----------------------
>
> Key: RANGER-1697
> URL: https://issues.apache.org/jira/browse/RANGER-1697
> Project: Ranger
> Issue Type: Improvement
> Components: plugins
> Reporter: Matt Gilman
> Assignee: Nikhil Purbhe
> Priority: Minor
> Fix For: 0.7.2
>
> Attachments: 0001-RANGER-1697.patch, RANGER-1697.patch
>
>
> Apache NiFi would like to update the service def file to ensure more
> consistent policy support between NiFi and Ranger. NiFi is in the process of
> introducing an improved Ranger authorizer that allows the policies to be
> viewed in NiFi UI for easier, in app, understanding of the policies
> configured in Ranger UI. This effort is being tracked with this JIRA [1].
> I would like to supply a patch with updates to the NiFi service def file.
> Thanks!
> [1] https://issues.apache.org/jira/browse/NIFI-4032
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
