When creating collection in SolrCloud, collection is available for queries and updates through all Solr nodes, in particular nodes that does not hold one of collection's cores. This is expected behaviour that works when using SolrJ client or HTTP requests.
When enabling authorization rules it seems that this behaviour is broken for HTTP requests:
- executing request to a node that holds part of the collection (core) obey to authorization rules as expected.
- other nodes respond with code 403 - unauthorized request.
SolrJ still works as expected.
Tested both with BasicAuthPlugin and KerberosPlugin authentication plugins.
1. Create a cloud made of 2 nodes (node_1, node_2).
2. Configure authentication and authorization by uploading following security.json file to zookeeper:
3. create 'test' collection with one shard on node_1.
The following requests expected to succeed but return 403 status (unauthorized request):
Authenticated 'solr' user requests works as expected. My guess is due to the special 'all' role.