[SOLR-15575] CollectionAdminRequest's processAndWait does not propagate the per-request basic auth credentials from the main request to RequestStatus and DeleteStatus used internally

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 9.0, 8.10
• Component/s: security
• Assignee: Timothy Potter
• Reporter: Timothy Potter
• Created: 03/Aug/21 15:22
• Updated: 28/Sep/21 20:27
• Resolved: 04/Aug/21 22:27

Description

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:

  @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);
     ...
  }

Issue Links

• links to: GitHub Pull Request #246
• links to: GitHub Pull Request #2547