[jira] [Updated] (SOLR-10627) Security API should not let users create permission with collection:null for per collection permissions

["Cassandra Targett (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-10627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cassandra Targett updated SOLR-10627:
-------------------------------------
    Component/s: Authorization

> 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
>          Components: Authorization
>            Reporter: Noble Paul
>            Assignee: Noble Paul
>            Priority: Major
>              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
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org