The Publish to SharePoint 2013 publisher will post documents to SharePoint 2013 index through HTTP posts.
Publish to SharePoint installs several components into Microsoft Internet Information Server (IIS) and SharePoint.
The publisher installs one service into IIS:
Aspire BDC Service (WCF)
This service is protected using NTLM authentication mechanisms. Any user accessing the service must be member of the AspireUsers Active Directory or a local Windows group.
The publisher installs two services into SharePoint 2013:
Aspire Notification Service (SOAP)
This service is deployed as a Farm Solution and is responsible for creating:
It also receives and forwards requests for crawling the Content Sources created by Aspire.
Security trimming is available within SharePoint 2013 itself. To make this work a SecurityTrimmerPre interface must be created. See [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” the security trimmer. With the exception of deny ACLs, the function of the ISecurityTrimmerPre module is always to add results to the result set, rather than to remove them. In this sense, it is the opposite of a security trimmer. It is critical to understand that, if the ISecurityTrimmerPre interface malfunctions, you will get no secure search results. If it was doing "classic" security trimming and 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 (LDAP, Lotus Notes, etc.)
Aspire is involved in both indexing and search workflows.
The Aspire SharePoint 2013 Publisher performs two steps:
Aspire optionally enhances the SharePoint 2013 document processing workflow by calling the Aspire Content Enrichment Webservices (CEWS) listener.
Each search request issued using the Search Service Application is routed through Aspire to add ACL restrictions to the query via the Security Pre-Trimmer.
Please review the SharePoint 2013 Publisher FAQ & Troubleshooting for any Known Issues.