You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2016/05/20 22:21:13 UTC
[jira] [Reopened] (SOLR-8970) SSLTestConfig behaves really stupid
if keystore can't be found
[ https://issues.apache.org/jira/browse/SOLR-8970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Rowe reopened SOLR-8970:
------------------------------
Reopening to backport to 6.0.1.
> 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.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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org