[
https://issues.apache.org/jira/browse/SOLR-10627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-10627:
------------------------------
Description:
Users end up creating permissions like
{code}
{
"collection":null,
"name": "update",
"role": "some-role"
}
{code}
They expect this to secure the update operations.
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}} . So,
just don't let users specify it. Throw an error
was:
Users end up creating permissions like
{code}
{
"collection":null,
"name": "update",
"role": "come-role"
}
{code}
They expect this to secure the update operations.
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}} . So,
just don't let users specify it. Throw an error
> 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
>
> Users end up creating permissions like
> {code}
> {
> "collection":null,
> "name": "update",
> "role": "some-role"
> }
> {code}
> They expect this to secure the update operations.
> 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}} .
> So, just don't let users specify it. Throw an error
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
