Solr 3.1 is being clever here; it's seeing arguments coming in that do not correspond to known schema fields, and presuming they are "automatic" fields. So when the schema is unmodified, you see these fields that Solr creates for you, with the attr_ prefix. They are created as being "stored", which is not good for access tokens since then you will see them in the response. I don't know if they are indexed or not, but I imagine not, which is also not good.
So following the instructions is still the right thing to do, I would say. Karl On Fri, Apr 22, 2011 at 3:24 PM, Kadri Atalay <atalay.ka...@gmail.com> wrote: > Hi Karl, > > There is one thing I noticed while following the example in chapter 4.: > Prior to making any changes into the schema.xml, I was able to see the > following security information in query responses: > ie: > > <doc> > - > <arr name="attr_allow_token_document"> > <str>TEQA-DC:S-1-3-0</str> > <str>TEQA-DC:S-1-5-13</str> > <str>TEQA-DC:S-1-5-18</str> > <str>TEQA-DC:S-1-5-32-544</str> > <str>TEQA-DC:S-1-5-32-545</str> > <str>TEQA-DC:S-1-5-32-547</str> > </arr> > - > <arr name="attr_allow_token_share"> > <str>TEQA-DC:S-1-1-0</str> > <str>TEQA-DC:S-1-5-2</str> > - > <str> > TEQA-DC:S-1-5-21-1212545812-2858578934-3563067286-1480 > </str> > </arr> > - > <arr name="attr_content"> > - > <str> > Autonomy ODBC Fetch Technical Brief 0506 > Technical Brief > > > But, after I modified the schema/xml, and added the following fields, > <!-- Security fields --> > <field name="allow_token_document" type="string" indexed="true" > stored="false" multiValued="true"/> > <field name="deny_token_document" type="string" indexed="true" > stored="false" multiValued="true"/> > <field name="allow_token_share" type="string" indexed="true" > stored="false" multiValued="true"/> > <field name="deny_token_share" type="string" indexed="true" > stored="false" multiValued="true"/> > > I longer see neither the attr_allow_token_document or the > allow_token_document fields.. > > Since same fields exist with attr_ prefix, should we need to add these new > field names into the schema file, or can we simply change ManifoldSecurity > to use attr_ fields ? > > Also, when Solr is running under Tomcat, I have to re-start the Solr App, or > re-start Tomcat to see the newly added indexes.. > > Any thoughts ? > > Thanks > > Kadri > > On Fri, Apr 22, 2011 at 12:53 PM, Karl Wright <daddy...@gmail.com> wrote: >> >> I don't believe Solr has yet officially released document access >> control, so you will need to use the patch for ticket 1895. >> Alternatively, the ManifoldCF in Action chapter 4 example has an >> implementation based on this ticket. You can get the code for it at >> >> https://manifoldcfinaction.googlecode.com/svn/trunk/edition_1/security_example. >> >> Thanks, >> Karl >> >> >> On Fri, Apr 22, 2011 at 11:45 AM, Kadri Atalay <atalay.ka...@gmail.com> >> wrote: >> > Hello, >> > >> > Does anyone know which version of Solr have implements the Document >> > Level >> > Access Control, or has it implemented (partially or fully) ? >> > Particularly issue #s 1834, 1872, 1895 >> > >> > Thanks >> > >> > Kadri >> > > >
