You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Gaurav Kumar (JIRA)" <ji...@apache.org> on 2015/12/23 20:36:46 UTC
[jira] [Commented] (SOLR-8439) Solr Security - Permission read does
not work as expected
[ https://issues.apache.org/jira/browse/SOLR-8439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070082#comment-15070082 ]
Gaurav Kumar commented on SOLR-8439:
------------------------------------
Is it possible to backport it to 5.3.1? We were trying to upgrade to 5.3.1 to get the new security features, please recommend a recommended version based on bug fixes related to security fixes.
> Solr Security - Permission read does not work as expected
> ---------------------------------------------------------
>
> Key: SOLR-8439
> URL: https://issues.apache.org/jira/browse/SOLR-8439
> Project: Solr
> Issue Type: Bug
> Components: security
> Affects Versions: 5.3.1
> Environment: Linux, Solr Cloud
> Reporter: Gaurav Kumar
> Priority: Critical
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> I enabled security on my solr cloud and added basic authentication and authorization to allow only specific users to read and update the records. What I observed that update works fine but read does not stop from anonymous access.
> On digging deeper I saw that RuleBasedAuthorizationPlugin.java has incorrectly defined the read permissions as follows:
> read :{" +
> " path:['/update/*', '/get']}," +
> It should be /select/* rather than /update/*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org