[RANGER-1446] Ranger Solr Plugin does not work when the collection list in the request is empty

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.7.0, 0.6.1, 0.6.2, 0.6.3
• Fix Version/s: 1.0.0, 0.7.1
• Component/s: plugins
• Assignee: Yan
• Reporter: Yan
• Created: 10/Mar/17 20:14
• Updated: 22/May/17 16:36
• Resolved: 13/Mar/17 16:02

Description

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.

Issue Links

• is broken by: RANGER-1095 Invert authorization logic in RangerSolrAuthorizer