You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-commits@lucene.apache.org by Apache Wiki <wi...@apache.org> on 2010/03/16 00:51:30 UTC

[Solr Wiki] Update of "SolrSecurity" by JanHoydahl

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "SolrSecurity" page has been changed by JanHoydahl.
The comment on this change is: Adding mention of LCF.
http://wiki.apache.org/solr/SolrSecurity?action=diff&rev1=11&rev2=12

--------------------------------------------------

  
  == Document Level Security ==
  
- Although Solr does not directly support Document level security, the SolrRequestHandler framework is easy to configure for your specific needs.
+ === Lucene Connector Framework ===
+ The Solr core does not aim to deal with Document level security. The recommended way to add document level security to your search is through Apache [[http://incubator.apache.org/connectors/|Lucene Connector Framework (LCF)]]. From LCF's WIKI we can read "LCF defines and fully supports a model of document security, so that each document listed in a search result from the back-end search engine is one that the current user is allowed to see".
+ 
+ 
+ === Roll your own ===
+ In case LCF do not solve your needs, the SolrRequestHandler framework is easy to configure for custom needs:
  
  If you need permission based authentication -- where user A can update document 1 and 2, but not 3 -- you will need to augment the request with user information.  Either you can add parameters to the query string (?u=XXX&p=YYY) or use a custom dispatcher filter that augments the context:
  {{{