[
https://issues.apache.org/jira/browse/SOLR-8970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-8970:
---------------------------
Attachment: SOLR-8970.patch
updated patch to compile against master -- but after working on other SSL test
related issues and getting more familiar with the code i realize what Joseph
suggested isn't hard at all -- it would just require a bit of refactoring in
how SSLConfig.createContextFactory works so that SSLTestConfig can override the
the method completely and produce it's own KeyStore object (instead of a path).
All the plumbing to load KeyStore objects from resources files in the
classpath already exists.
I'll look into this soon.
> 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
> Attachments: 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
