lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Rowe (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SOLR-7449) solr/server/etc/jetty-https-ssl.xml hard codes the key store file and password rather than pulling them from the sysprops defined in solr/bin/solr.in.{sh,bat}
Date Wed, 22 Apr 2015 22:08:58 GMT
Steve Rowe created SOLR-7449:
--------------------------------

             Summary: solr/server/etc/jetty-https-ssl.xml hard codes the key store file and
password rather than pulling them from the sysprops defined in solr/bin/solr.in.{sh,bat}
                 Key: SOLR-7449
                 URL: https://issues.apache.org/jira/browse/SOLR-7449
             Project: Solr
          Issue Type: Bug
    Affects Versions: 5.1
            Reporter: Steve Rowe


[~shalinmangar] pointed out this issue out to me.  

The hard-coded values in {{jetty-https-ssl.xml}} are the same as the ones in the tutorial,
so people creating the keystore as described in the tutorial are able to run Solr in SSL mode.

Also {{jetty-https-ssl.xml}} doesn't configure a trust store (or a password for it), so there's
no way currently to have a different trust store from the key store.



--
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


Mime
View raw message