That's good to hear, and yes I'd like to collaborate on this. I'm off on holiday for the next couple of weeks, but will definitely pick up on this and open a JIRA ticket when I return.
Cheers, Colin -----Original Message----- From: Karl Wright [mailto:daddy...@gmail.com] Sent: 16 April 2012 18:45 To: connectors-user@incubator.apache.org Subject: Re: Document level security for database documents Adding security support to the JDBC connector has been on the table for a long while but there has been no good "use case" up until now. If you would like to collaborate on developing this feature, please open a new ticket, and include what your preferred schema is for the access tokens that the JDBC connector would supply. We can work on coming up with as general a solution as possible given that starting point. Thanks, Karl On Mon, Apr 16, 2012 at 1:40 PM, <colin.ander...@akersolutions.com> wrote: > The ManifoldCF docs say that document-level security isn't supported > with the JDBC database connector. > > > > This is pretty much what I want to achieve - I have tables of > documents, tables of Active Directory usernames, and tables that join the two > together. > > > > Do I have any options do I have to do this with ManifoldCF? If not, I > can write something custom that will post directly to Solr, but since > I'm planning on using ManifoldCF to crawl other content too, I'd > rather use ManifoldCF if I can. > > > > Cheers, > > > > Colin > > > This e-mail and any attachment are confidential and may be privileged > or otherwise protected from disclosure. It is solely intended for the > person(s) named above. If you are not the intended recipient, any > reading, use, disclosure, copying or distribution of all or parts of > this e-mail or associated attachments is strictly prohibited. If you > are not an intended recipient, please notify the sender immediately by > replying to this message or by telephone and delete this e-mail and > any attachments permanently from your system. This e-mail and any attachment are confidential and may be privileged or otherwise protected from disclosure. It is solely intended for the person(s) named above. If you are not the intended recipient, any reading, use, disclosure, copying or distribution of all or parts of this e-mail or associated attachments is strictly prohibited. If you are not an intended recipient, please notify the sender immediately by replying to this message or by telephone and delete this email and any attachments permanently from your system.
