[
https://issues.apache.org/jira/browse/SOLR-8970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15295211#comment-15295211
]
ASF subversion and git services commented on SOLR-8970:
-------------------------------------------------------
Commit 3cc008253513977d1554de3be1c34f35bc4461ae in lucene-solr's branch
refs/heads/branch_6_0 from Chris Hostetter
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=3cc0082 ]
SOLR-8970: Change SSLTestConfig to use a keystore file that is included as a
resource in the test-framework jar so users subclassing SolrTestCaseJ4 don't
need to preserve magic paths
(cherry picked from commit 76063648ae05a935459f2ea5ed53c4df1caa713d)
> SSLTestConfig behaves really stupid if keystore can't be found
> --------------------------------------------------------------
>
> Key: SOLR-8970
> URL: https://issues.apache.org/jira/browse/SOLR-8970
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Assignee: Hoss Man
> Fix For: 6.0.1, 6.1, master (7.0)
>
> Attachments: SOLR-8970.patch, SOLR-8970.patch, SOLR-8970.patch
>
>
> The SSLTestConfig constructor lets the call (notable SolrTestCaseJ4) tell it
> wether clientAuth should be used (note SolrTestCaseJ4 calls this boolean
> "trySslClientAuth") but it has a hardcoded assumption that the keystore file
> it can use (for both the keystore and the truststore) will exist at a fixed
> path in the solr install.
> when this works, it works fine - but if end users subclass/reuse
> SolrTestCaseJ4 in their own projects, they may do so in a way that prevents
> the SSLTestConfig keystore assumptions from being true, and yet they won't
> get any sort of clear error.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
