[
https://issues.apache.org/jira/browse/SOLR-18132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18144486#comment-18144486
]
dmitri maziuk commented on SOLR-18132:
--------------------------------------
In this instance we have an old v.8 cluster without SSL and added v.9 Solr to
the existing zookeeper. The problem is it all "appeared to" work until I got to
collection creation. Either it should have failed right away e.g. failed to
connect to zk from the start, or it should work all the way with 2 separate
configs. At the very least it should be spelled out in TFM that you can't do
one without the other.
Generally speaking we need SSL to encrypt Solr usernames/passwords. If there
are no secret creds passed passed between Solr and Zk, then why encrypt that
traffic?
As I mentioned in the e-mail thread, if/when I get to rebuild this cluster
properly, I'll be tempted to off-load auth and SSL to the ingress node and not
bother with any of this in the first place..
> SSL and external zookeeper
> ---------------------------
>
> Key: SOLR-18132
> URL: https://issues.apache.org/jira/browse/SOLR-18132
> Project: Solr
> Issue Type: Bug
> Affects Versions: 9.10.1
> Reporter: dmitri maziuk
> Priority: Major
>
> In a 9.10.1 cluster with external zookeeper, SSL enabled for Solr but not for
> ZK inter-node communication:
> * Admin UI "Cloud" section works
> * Configset API work
> * Enabling auth via CLI works
> Collection creation fails with unhelpful "IOException" talking to the nodes.
> Turning SSL off fixes that.
> The bug is that if SSL is an all-or-nothing proposition, it should fail right
> away for *all* ZK communications and not "work up to a point" like it does
> now.
> Preferably, of course, it should work with SSL enabled for Solr but not for
> ZK: the cluster lives in its own sandbox and does not really need SSL
> internally. SSL is enabled only because authentication is enabled on client
> connections to Solr nodes and sending unencrypted creds is bad for security
> audits.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]