Every situation is different, and that design is what Solr used to
recommend before we added the rule based auth plugin. It all depends on
how critical internal security is vs external security. Very large
companies sometimes have more risk from internal threats, small companies
can often afford to trust internal folks more. The intent of the auth
plugins we have is to allow for internal security, though I think they
deviate from expected norms and are more complex than they need to be.

On Fri, Oct 30, 2026 at 4:31 PM Dmitri Maziuk <[email protected]>
wrote:

> On 10/30/26 15:00, Gus Heck wrote:
> ...> If you are unable to protect everything but queries with
> > blockUnknown:false, a rule for all, and * as the required role for
> queries
> > then you may have found a bug.
> I haven't tried and TBH I am not planning to. If I get a go-ahead to
> rebuild our current cluster I'll be very tempted to off-load both SSL
> and ACLs to the proxy node and leave the backend "woefully insecure".
> (And then our security theater won't complain about "information
> disclosure" defaults and "untrusted" self-signed certificates and the
> rest of it.)
>
> (I get that Solr has to have it for standalone deployments etc. where
> people don't have that option.)
>
> Dima
>


-- 
http://www.needhamsoftware.com (work)
https://a.co/d/b2sZLD9 (my fantasy fiction book)

Reply via email to