[
https://issues.apache.org/jira/browse/SOLR-10627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-10627:
------------------------------
Labels: authorization-plugin security (was: authorization-plugin)
> Security API should not let users create permission with collection:null for
> per collection permissions
> -------------------------------------------------------------------------------------------------------
>
> Key: SOLR-10627
> URL: https://issues.apache.org/jira/browse/SOLR-10627
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Assignee: Noble Paul
> Labels: authorization-plugin, security
>
> Users end up creating permissions like
> {code}
> {
> "collection":null,
> "name": "update",
> "role": "some-role"
> }
> {code}
> They expect this to secure the update operations. This does not work and does
> not protect any operation
> The security API should throw an error when such a permission is created .
> For the well-known permissions, we already know the value of {{collection}} .
>
> * if {{collection:null}} is specified for a per-collection permission, that
> should be ignored
> * for permissions where collection is not required , such as
> {{collection-admin-edit}} , {{security-edit}} , value of collection is null
> anyway , no other value should be allowed to be specified
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
