It is not that solr is over protected, it is just that the clients,
SolrJ as well as bin/solr are not provided with basic auth
capabilities.
I have opened a ticket to track this
https://issues.apache.org/jira/browse/SOLR-8048
On Sat, Sep 12, 2015 at 7:14 PM, Dan Davis wrote:
> Noble,
>
> You sh
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
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,
