I figured out you can disable the core admin in solr.xml, but then it
breaks the admin as apparently it relies on that.
I tried tomcat security but haven't been able to make it work
I think as this point I may just write a query/debugging app that the
developers could use
On 11/13/2012 07:12
Basic http authentication can use to filter the accesses to different
urlas you want, so you can allow access
to the Query, Analysis, etc and Admin ban
2012/11/13 Erick Erickson
> Slap them firmly on the wrist if they do?
>
> The Solr admin is really designed with trusted users in mind. There a
Slap them firmly on the wrist if they do?
The Solr admin is really designed with trusted users in mind. There are no
provisions that I know of for securing some of the functions.
Your developers have access to the Solr server through the browser, right?
They can do all of that via URL, see: http:
I really like the new admin in solr 4.0, but specifically I don't want
developers to be able to unload, rename, swap, reload, optimize, or add
core.
Any ideas on how I could still give access to the rest of the admin
without giving access to these? It is very helpful for them to have
access t