Noble, You should also look at this if it is intended to be more than an internal API. Using the minor protections I added to test SOLR-8000, I was able to reproduce a problem very like this:
bin/solr healthcheck -z localhost:2181 -c mycollection Since Solr /select is protected... On Sat, Sep 12, 2015 at 9:40 AM, Dan Davis <dansm...@gmail.com> wrote: > It seems that you have secured Solr so thoroughly that you cannot now run > bin/solr status! > > bin/solr has no arguments as yet for providing a username/password - as a > mostly user like you I'm not sure of the roadmap. > > I think you should relax those restrictions a bit and try again. > > On Fri, Sep 11, 2015 at 5:06 AM, Merlin Morgenstern < > merlin.morgenst...@gmail.com> wrote: > >> I have secured solr cloud via basic authentication. >> >> Now I am having difficulties creating cores and getting status >> information. >> Solr keeps telling me that the request is unothorized. However, I have >> access to the admin UI after login. >> >> How do I configure solr to use the basic authentication credentials? >> >> This is the error message: >> >> /opt/solr-5.3.0/bin/solr status >> >> Found 1 Solr nodes: >> >> Solr process 31114 running on port 8983 >> >> ERROR: Failed to get system information from http://localhost:8983/solr >> due >> to: org.apache.http.client.ClientProtocolException: Expected JSON response >> from server but received: <html> >> >> <head> >> >> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> >> >> <title>Error 401 Unauthorized</title> >> >> </head> >> >> <body><h2>HTTP ERROR 401</h2> >> >> <p>Problem accessing /solr/admin/info/system. Reason: >> >> <pre> Unauthorized</pre></p><hr><i><small>Powered by >> Jetty://</small></i><hr/> >> >> >> </body> >> >> </html> >> > >
