You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Yan (JIRA)" <ji...@apache.org> on 2017/03/10 20:33:04 UTC
[jira] [Commented] (RANGER-1446) Ranger Solr Plugin does not work
when the collection list in the request is empty
[ https://issues.apache.org/jira/browse/RANGER-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905658#comment-15905658 ]
Yan commented on RANGER-1446:
-----------------------------
A review request is posted at https://reviews.apache.org/r/57519/.
Since this seeming severe issue is blocking virtually all Solr plugin tests at our IBM site, I appreciate a quick review/commit action from the community and/or [~coheigea] in particular.
Thanks!
> Ranger Solr Plugin does not work when the collection list in the request is empty
> ---------------------------------------------------------------------------------
>
> Key: RANGER-1446
> URL: https://issues.apache.org/jira/browse/RANGER-1446
> Project: Ranger
> Issue Type: Bug
> Components: plugins
> Affects Versions: 0.7.0, 0.6.1, 0.6.2, 0.6.3
> Reporter: Yan
> Assignee: Yan
> Priority: Critical
> Fix For: master
>
> Attachments: Ranger-1446.patch
>
>
> The fix of Ranger-1095 set the initial value of "denied" to "true" from the previous "false". One impact of this change is that, when context.getCollectionRequests() is empty which could be the case in many invocations Solr makes to Ranger on authorization per client request, the permission is plainly denied without going to Ranger policy engine. So the fix changed the default behavior related "denied".
> A proper fix of Ranger-1095 IMO should be just to set the "denied" to "true" in the catch block without changing the initial value of the variable.
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)