You could also use one of the proxy scripts, such as http://code.google.com/p/solr-php-client/, which is coincidentally linked (eventually) from Michael's suggested SolrSecurity URL.
-----Original Message----- From: michael.boom [mailto:my_sky...@yahoo.com] Sent: 22 November 2013 14:53 To: solr-user@lucene.apache.org Subject: Re: How to work with remote solr savely? http://wiki.apache.org/solr/SolrSecurity#Path_Based_Authentication Maybe you could achieve write/read access limitation by setting path based authentication: The update handler "/solr/core/update" should be protected by authentication, with credentials only known to you. But then of course, your indexing client will need to authenticate in order to add docs to solr. Your select handler "/solr/core/select" could then be open or protected by http auth with credentials open to developers. That's the first idea that comes to mind - haven't tested it. If you do, feedback and let us know how it went. ----- Thanks, Michael -- View this message in context: http://lucene.472066.n3.nabble.com/How-to-work-with-remote-solr-savely-t p4102612p4102618.html Sent from the Solr - User mailing list archive at Nabble.com.
