That said, it might be nice with a wiki-page (or something) explaining
how it can be done, including maybe concrete cases about exactly how it
has been done on different installations around the world using Solr
On 14/04/15 14:03, Per Steffensen wrote:
Hi
I might misunderstand you, but if you
From: Per Steffensen [mailto:st...@designware.dk]
Sent: Tuesday, April 14, 2015 8:04 AM
To: solr-user@lucene.apache.org
Subject: Re: Securing solr index
Hi
I might misunderstand you, but if you are talking about securing the actual
files/folders of the index, I do not think this is a Solr/Lucene co
Hi
I might misunderstand you, but if you are talking about securing the
actual files/folders of the index, I do not think this is a Solr/Lucene
concern. Use standard mechanisms of your OS. E.g. on linux/unix use
chown, chgrp, chmod, sudo, apparmor etc - e.g. allowing only root to
write the fo
Where you want true Role-Based Access Control (RBAC) on each index (core or
collection), one solution is to buy Solr Enterprise from LucidWorks.
My personal practice is mostly dictated by financial decisions:
- Each core/index has its configuration directory in a Git
repository/branch where
Hi,
We are having the solr index maintained in a central server and multiple users
might be able to access the index data.
May I know what are best practice for securing the solr index folder where
ideally only application user should be able to access. Even an admin user
should not be able to
