Authentication does work and authorization for general is working fine. But
nothing authorization works when specified certain collection. That's so
frustrating. It is weird that even I just do simple "path":"/*" won't do
anything if I add "collection":"a".
--
Sent from: http://lucene.472066.n3.
I am using standalone Solr 7.4.0. Are you using cloud or standalone? Not sure
if that cause the problem or not.
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
I tried to replace "/select" with "/*" but user B can still access collection
A.
"permissions":[
{
"name":"security-edit",
"role":"admin",
"index":1},
{
"name":"PermA",
"collection":CollectionA"",
"path":"/*",
"role":["ReadColl
Thank you for your replay. I use your format and failed. User2 can still
visit collection "name"
Could that because I am using standalone Solr not Solrcloud?
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Yes, I tried only /select. Doesn't work as well.
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hi,
I am using standalone Solr 7.4. Right now I have 2 collections A and B.
Users a and b. I want to let only a can read and query A, b can read and
query B. But it doesn't work. I have tried similar in
https://lucidworks.com/2017/04/14/securing-solr-tips-tricks-and-other-things-you-really-need-to-
Hi Antony,
Have you solved this? I am facing the same thing. Other users can still do
/select after I set the permission path and collection.
Best,
Rick
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
