[ 
https://issues.apache.org/jira/browse/SOLR-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867135#action_12867135
 ] 

Karl Wright commented on SOLR-1834:
-----------------------------------

I've attached what I think to be the correct code to structure the LCF security 
support as two plugins into this framework.  The first is a security provider, 
the second is a model.  In order to use this with LCF, you still need to set up 
a schema consistent with SOLR-1895, and you would also need the schema addition 
that this framework provides.

The SOLR-1834-with-LCF.patch file is an SVN diff against Solr trunk.  I needed 
to make a number of changes to build.xml to get it to work in the current trunk 
environment.  Also, I needed to comment out the @override commands for some 
reason - but still, everything looked good.


> Document level security
> -----------------------
>
>                 Key: SOLR-1834
>                 URL: https://issues.apache.org/jira/browse/SOLR-1834
>             Project: Solr
>          Issue Type: New Feature
>          Components: SearchComponents - other
>    Affects Versions: 1.4
>            Reporter: Anders Rask
>         Attachments: html.rar, SOLR-1834-with-LCF.patch, SOLR-1834.patch
>
>
> Attached to this issue is a patch that includes a framework for enabling 
> document level security in Solr as a search component. I did this as a Master 
> thesis project at Findwise in Stockholm and Findwise has now decided to 
> contribute it back to the community. The component was developed in spring 
> 2009 and has been in use at a customer since autumn the same year.
> There is a simple demo application up at 
> http://demo.findwise.se:8880/SolrSecurity/ which also explains more about the 
> component and how to set it up.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to