As described in the overview, in order to avoid the overhead of parsing query result for applying security checks, openutils-mgnlcriteria supply an implementation of jackrabbit SearchIndex which applies ACLs automatically before executing any query.

You can configure it in the jackrabbit configuration file, by replacing the standard org.apache.jackrabbit.core.query.lucene.SearchIndex.

Just look at your jackrabbit configuration file to replace any occurrence of:

<SearchIndex class="org.apache.jackrabbit.core.query.lucene.SearchIndex">

 

with:

<SearchIndex class="net.sourceforge.openutils.mgnlcriteria.jcr.query.lucene.AclSearchIndex">

 

Please note that this ACL-enabled search index is pretty experimental, due to the complexity of the task. Just don't configure it if you don't need it, and please report any problem you may find with particular query/acl combination. 

 

Jackrabbit allows you to tweak several aspect of indexing, an important feature that probably is not well known by most magnolia users.

With an indexing configuration file you may for example configure how content is aggregated for full text search (e.g. aggregate paragraphs in parent pages), removing certain properties from full text search (e.g. don't let users search for the author name), configuring score and so on.

You can setup an indexing configuration by adding the following parameter to the SearchIndex:

    <SearchIndex class="...">
      <param name="indexingConfiguration" value="/index_configuration.xml" />

You can  find more details on the format or the indexing configuration file on the jackrabbit wiki at http://wiki.apache.org/jackrabbit/IndexingConfiguration