Apache Solr Reference Guide Covering Apache Solr 6.0

pre-defined permission to a role.
update-permission: update some attributes of an existing permission definition.
delete-permission: remove a permission definition.
Permissions need to be created if they are not on the list of pre-defined permissions above.
Several properties can be used to define your custom permission.
Property
name
collection
Description
The name of the permission. The name will be used to update or delete the permission later.
The collection or collections the permission will apply to.
When the path that will be allowed is collection-specific, such as when setting permissions to allow
use of the Schema API, omitting the collection property will allow the defined path and/or method
for all collections. However, when the path is one that is non-collection-specific, such as the
Collections API, the collection value must be null.
path A request handler name, such as /update or /select. A wild card is supported, to allow for all
paths as appropriate (such as, /update/*).
method
params
HTTP methods that are allowed for this permission. You could allow only GET requests, or have a
role that allows PUT and POST requests. The method values that are allowed for this property are
GET, POST, PUT, DELETE and HEAD.
The names and values of request parameters. This property can be omitted if all request
parameters are allowed, but will restrict access only to the values provided if defined.
For example, this property could be used to limit the actions a role is allowed to perform with the
Collections API. If the role should only be allowed to perform the LIST or CLUSTERSTATUS
requests, you would define this as follows:
"params": {
"action": [LIST, CLUSTERSTATUS]
}
before
role
This property allows ordering of permissions. The value for this property is the name of the
permission that this new permission should be placed before in security.json.
The name of the role(s) to give this permission. This name will be used to map user IDs to the role
to grant these permissions. The value can be wild card such as (*), which means that any user is
OK, but no user is NOT OK.
The following would create a new permission named "collection-mgr" that is allowed to create and list collections.
The permission will be placed before the "read" permission. Note also that we have defined "collection as null,
this is because requests to the Collections API are never collection-specific.
Apache Solr Reference Guide 6.0
524