Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
Subject: Re: Which Solr releases contain SOLR-4470 (Security for
 inter-solr-node requests)
From: =?utf-8?Q?Jan_H=C3=B8ydahl?= <jan.asf@cominvent.com>
In-Reply-To: 
 <9CA61F0598F2774FBA4540A79DE3DB671042694E76@sho-p-excmbx-01.sentry.com>
Date: Mon, 3 Nov 2014 23:33:23 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <05DD07B7-7D82-4020-AFFF-310523BEF930@cominvent.com>
References: 
 <9CA61F0598F2774FBA4540A79DE3DB671042694E76@sho-p-excmbx-01.sentry.com>
To: solr-user@lucene.apache.org

You find the answer to such questions by looking at the state of the =
JIRA issue
https://issues.apache.org/jira/browse/SOLR-4470

Staus: Open
Fix version: Trunk

Which means that this feature is not included in any released Solr =
version (yet).

--
Jan H=C3=B8ydahl, search solution architect
Cominvent AS - www.cominvent.com

> 3. nov. 2014 kl. 22.39 skrev Yuan Jerry <Jerry.Yuan@sentry.com>:
>=20
> I am currently working on SolrCloud and its related security =
configurations for securing Solr web applications using HTTP Basic =
Authentication mechanism. Among the Solr nodes inside the SolrCloud =
clustered env, there seem to be existing some inter-solr-node =
communication issues due to the security configurations, which are the =
HTTP Authentication errors. Based on my research, the patch SOLR-4470 =
(Security for inter-solr-node requests) would be ideal for resolving =
these issues (please refer to the address: =
https://wiki.apache.org/solr/SolrSecurity#Security_for_inter-solr-node_req=
uests). However, it seems to me that these security patches are =
out-of-box additions to the current Solr source codebase, which don't =
seem to be available in the recent Solr releases.
>=20
> If someone could point out which Solr releases or the jars from some =
online repositories that contain this patch, it would be appreciated =
very much.
>=20
> Jerry
>=20
>=20
> This e-mail is confidential.  If you are not the intended recipient, =
you must not disclose or use the information contained in it. If you =
have received this e-mail in error, please tell us immediately by return =
e-mail and delete the document. No recipient may use the information in =
this e-mail in violation of any civil or criminal statute. Sentry =
disclaims all liability for any unauthorized uses of this e-mail or its =
contents. Sentry accepts no liability or responsibility for any damage =
caused by any virus transmitted with this e-mail.