[ 
https://issues.apache.org/jira/browse/SOLR-11678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267398#comment-16267398
 ] 

Shawn Heisey commented on SOLR-11678:
-------------------------------------

FYI:  Solr itself doesn't have any SSL-related code.  All of that is in Jetty, 
which Solr includes and uses.

My initial guess, which I will fully admit could be wrong, is that either Jetty 
doesn't support what you're doing, or that we haven't taken your configuration 
and given it to Jetty correctly.

I can't tell exactly how you have installed/started Solr, and exactly what file 
you are editing to set the SSL passwords.  Can you provide that information?


> SSL not working if store and key passwords are different
> --------------------------------------------------------
>
>                 Key: SOLR-11678
>                 URL: https://issues.apache.org/jira/browse/SOLR-11678
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: security
>    Affects Versions: 6.6.2
>            Reporter: Constantin Bugneac
>
> If I specify different passwords for store and key then Solr fails to read 
> certificate from JKS file with the below error.
> Example:
> SOLR_SSL_KEY_STORE_PASSWORD: "secret1"
> SOLR_SSL_TRUST_STORE_PASSWORD: "secret2"
> If I set the same password for both - it works just fine.
> Tested with the docker image 6.6.2 available here 
> https://hub.docker.com/_/solr/
> I don't know whether this is JAVA nuance or Solr implementation issue but 
> from security point of view there there is no point to have the same password 
> assigned for both the key store and private key bound to specific certificate.
> Expected behaviour: It should allow to specify different passwords.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to