[
https://issues.apache.org/jira/browse/SOLR-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15440819#comment-15440819
]
Susheel Kumar commented on SOLR-9188:
-------------------------------------
Yes, Jan. The The cluster in my case works fine without any issue and infact we
moved up to three environment (development, functional & performance) with QA
certified and didn't notice any issue until one developer noticed these error
messages in Logs.
Removing blockUnknown doesn't help as it then allows anyone to access Solr
directly without challenging with user / pwd.
The Solr Cluster in our case has multiple shards.
Please let me know if i can provide any more details.
Thanks,
Susheel
> BlockUnknown property makes inter-node communication impossible
> ---------------------------------------------------------------
>
> Key: SOLR-9188
> URL: https://issues.apache.org/jira/browse/SOLR-9188
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 6.0
> Reporter: Piotr Tempes
> Priority: Critical
> Labels: BasicAuth, Security
> Attachments: solr9188-errorlog.txt
>
>
> When I setup my solr cloud without blockUnknown property it works as
> expected. When I want to block non authenticated requests I get following
> stacktrace during startup (see attached file).
--
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
