[ https://issues.apache.org/jira/browse/SOLR-9028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262906#comment-15262906 ]
ASF subversion and git services commented on SOLR-9028: ------------------------------------------------------- Commit 791d1e73933a88ef78a06a529d5dcb2fd9e01807 in lucene-solr's branch refs/heads/master from [~hossman_luc...@fucit.org] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=791d1e7 ] SOLR-9028: Fixed some test related bugs preventing SSL + ClientAuth from ever being tested > fix bugs in (add sanity checks for) SSL clientAuth testing > ---------------------------------------------------------- > > Key: SOLR-9028 > URL: https://issues.apache.org/jira/browse/SOLR-9028 > Project: Solr > Issue Type: Bug > Reporter: Hoss Man > Assignee: Hoss Man > Attachments: SOLR-9028.patch, SOLR-9028.patch, SOLR-9028.patch, > SOLR-9028.patch, SOLR-9028.patch, SOLR-9028.patch, os.x.failure.txt > > > While looking into SOLR-8970 i realized there was a whole heap of problems > with how clientAuth was being handled in tests. Notably: it wasn't actaully > being used when the randomization selects it (aparently due to a copy/paste > mistake in SOLR-7166). But there are few other misc issues (improper usage > of sysprops overrides for tests, missuage of keystore/truststore in test > clients, etc..) > I'm working up a patch to fix all of this, and add some much needed tests to > *explicitly* verify both SSL and clientAuth that will include some "false > positive" verifications, and some "test the test" checks. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org