(d) What is your preferred schema for access tokens in the database? a joined table, or a delimiter-separated list?(c) Are there multiple levels of ACL required (e.g. document, folder, share)?(b) Do you need support for both "allow" and "deny" ACLs?(a) What authority(s) do you hope to use to secure JDBC-based document content?For a start, can you let me know the following:Hi Alejandro,If you are hoping to get security tokens from each document row in the database, then we should talk further and I will develop a patch for you that works in a way that is consistent with your problem. I've created a ticket, CONNECTORS-1089, for tracking work on this feature.
The reason you are confused about document security in JDBC is because, heretofore, nobody has implemented document security using JDBC. We've been waiting for quite a while for a user who needs this functionality, so that we develop it properly.
KarlOn Thu, Oct 30, 2014 at 12:37 PM, Alejandro Calbazana <email@example.com> wrote:- Auth connector, specifying user query and access token queryI'm getting started with ManifoldCF and I'm scratching my head a little with how to get access tokens into my indexed content using a JDBC repository. Here is my setup:Hello,- JDBC repository connector, indicating which authority group to use- Solr output connector- Job tying the connectors together indicating the queries for content IDs and content dataWhere do I instruct Manifold on how where obtain access tokens for the content that it is crawling? I see that there is a "security" tab in the job setup that allows me to specify access tokens, but this is static. My content will have different tokens associated with it per row. How do I accomplish this? Is this a place where I need to add custom code to fetch the authorization detail and apply it to content?Any guidance is greatly appreciated!Thanks,