Restrictions

Important limitations and assumptions of the plugin:

• Installation of the plug-in plugin requires administrator permissions to run the deployment scripts from the SharePoint Management Shell (PowerShell).
• While a single installation of the plug-inplugin's .wsp file is necessary, a separate execution of the model deployment script is needed for each different Content Source that was published into STageR.

Architecture

SharePoint 2013 Components

StagerBDCPlugin

The plugin is deployed as a .wsp file that gets deployed as a global farm solution.  It It implements the SharePoint 's BDC standard for custom connectors and gets executed from a SharePoint content source to extract the contents from STageR and hand them to SharePoint for indexing.

Security Trimming

Security trimming is available within SharePoint 2013 itself. To make this work, a SecurityTrimmerPre interface must be created , (see security trimming Security Trimming for Search in SharePoint Server 2013).

The ISecurityTrimmerPre interface adds claims to the query , prior to the security trimming, ; so it executes “pre” (prior to) the security trimmer. With the exception of deny ACLs, the function of the ISecurityTrimmerPre module is always to add always add results to the result set, not rather than to remove them. In this sense, it is the opposite of a security trimmer.

It What is critical to understand is, that if the ISecurityTrimmerPre interface malfunctions, then you get no secure search results. (If it were doing performed "classic" security trimming , and it malfunctioned, then you would get back extra unauthorized results.) On each search request, the Security Pre-Trimmer is invoked to enhance the search query with ACL information. This information is retrieved from an Aspire group expander Group Expander (LDAP, Lotus Notes ...)