Hello, Can you post this question to u...@manifoldcf.apache.org too?
--- On Mon, 1/28/13, eShard <zim...@yahoo.com> wrote: > From: eShard <zim...@yahoo.com> > Subject: Multicore search with ManifoldCF security not working > To: solr-user@lucene.apache.org > Date: Monday, January 28, 2013, 6:16 PM > Good morning, > I used this post here to join to search 2 different cores > and return one > data set. > http://stackoverflow.com/questions/2139030/search-multiple-solr-cores-and-return-one-result-set > The good news is that it worked! > The bad news is that one of the cores is Opentext and the > ManifoldCF > security check isn't firing! > So users could see documents that they aren't supposed to. > The opentext security works if I call the core handler > individually. it > fails for the merged result. > I need to find a way to get the AuthenticatedUserName > parameter to the > opentext core. > Here's my /query handler for the merged result > <requestHandler name="/query" > class="solr.SearchHandler"> > > <lst name="defaults"> > <str name="q.alt">*:*</str> > > <str name="fl">id, attr_general_name, > attr_general_owner, > attr_general_creator, attr_general_modifier, > attr_general_description, > attr_general_creationdate, attr_general_modifydate, > solr.title, > content, category, link, pubdateiso > </str> > <str > name="shards">localhost:8080/solr/opentext/,localhost:8080/solr/Profiles/</str> > </lst> > <arr > name="last-components"> > > <str>manifoldCFSecurity</str> > </arr> > </requestHandler> > > As you can see, I tried calling manifoldCFSecurity first and > it didn't work. > I was thinking perhaps I can call the shards directly in the > URL and put the > AuthenticatedUserName on the opentext shard but I'm getting > pulled in > different directions currently. > > Can anyone point me in the right direction? > Thanks, > > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Multicore-search-with-ManifoldCF-security-not-working-tp4036776.html > Sent from the Solr - User mailing list archive at > Nabble.com. >