[
https://issues.apache.org/jira/browse/SOLR-7449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar resolved SOLR-7449.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 5.2
Trunk
Assignee: Shalin Shekhar Mangar
Fixed as part of SOLR-4839 on trunk and branch_5x. Thanks Steve!
> 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
> Assignee: Shalin Shekhar Mangar
> Fix For: Trunk, 5.2
>
>
> [~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: [email protected]
For additional commands, e-mail: [email protected]
