Timothy Potter created SOLR-15575:
-------------------------------------
Summary: CollectionAdminRequest's processAndWait does not
propagate the per-request basic auth credentials from the main request to
RequestStatus and DeleteStatus used internally
Key: SOLR-15575
URL: https://issues.apache.org/jira/browse/SOLR-15575
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Components: security
Reporter: Timothy Potter
Assignee: Timothy Potter
Here's a basic use case that fails on 8x because the basic auth credentials
supplied on the {{Create}} request do not propagate to the {{RequestStatus}}
and {{DeleteStatus}} objects used internally for the {{waitFor}}:
{code}
@Test
public void testCreateCollAsync() throws Exception {
CollectionAdminRequest.Create create =
CollectionAdminRequest.createCollection(collectionName, "conf", 1, 2,
0, 0);
create.setMaxShardsPerNode(2);
withBasicAuth(create).processAndWait(cluster.getSolrClient(), 5);
waitForState("Expected collection to be created with 1 shard and " + 2 + "
replicas",
collectionName, clusterShape(1, 2));
DocCollection docCollection =
assertNumberOfReplicas(collectionName, 2, 0, 0, false, true);
...
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
