[SOLR-15202] Rule-Based Authorization Plugin parameter for core, not just collection, for non-cluster installations

• Type: Wish
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 8.8.1
• Component/s: Authorization

Environment

Debian Buster, openjdk 11, Solr 8.8.1 stand-alone, installed as a service

• Assignee: Unassigned
• Reporter: Ken Liccardo
• Created: 26/Feb/21 21:17
• Updated: 12/Apr/21 20:17

Description

I was trying to limit access to specific CORES but as I was reading the RuleBasedAuthorizationPlugin documentation I conflated the terms "core" and "collection", and was wondering why configuring permissions by core name used in the collection parameter wasn't working.  I've used Solr for years as stand-alone but somehow this distinction (core vs collection; I understand now that the latter is only used in solr clusters) escaped me while reading the Authorization documentation.  Then I had an "aha" moment when I realized my confusion in terms.  So, I don't know if it is difficult to add authorization by core for us stand-alone users.  Or, perhaps allow the use of full paths, up to the endpoint, such as "solr/core1/select" instead of just "/select", for the "path" parameter.

 

Thanks.