[ 
https://issues.apache.org/jira/browse/SOLR-10699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015506#comment-16015506
 ] 

Noble Paul edited comment on SOLR-10699 at 5/18/17 9:46 AM:
------------------------------------------------------------

I don't think we have a very user friendly system in Solr. It's quite powerful 
but most of the times it's tasteless. My point is 99.99% of the time nobody is 
going to use a different authz plugin. So, it's going to be used only by a 
power user. We don't have to tell the normal users that it's pluggable, they 
just don't need to know it. This whole pluggability business is an annoyance to 
most users.  


was (Author: noble.paul):
I don't think we have a very user friendly system in Solr. It's quite friendly 
but most of the times it's tasteless. My point is 99.99% of the time nobody is 
going to use a different authz plugin. So, it's going to be used by a power 
user. We don't have to tell the normal users that it's pluggable, they just 
don't need to know it. This whole pluggability business is an annoyance to most 
users.  

> make it optional to specify authorization plugin class name
> -----------------------------------------------------------
>
>                 Key: SOLR-10699
>                 URL: https://issues.apache.org/jira/browse/SOLR-10699
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: security
>            Reporter: Noble Paul
>            Assignee: Noble Paul
>
> It is unlikely that users specify anything other than  
> {{"class":"solr.RuleBasedAuthorizationPlugin"}} for authorization. So , if 
> nothing is specified we should take the default as 
> {{solr.RuleBasedAuthorizationPlugin}}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to