Security trimming is available within SharePoint itself. To make this work, a SecurityTrimmerPre interface must be created.
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 to always 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, then you get no secure search results. (If it performed "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 ...)
The following items are required by this component:
- SharePoint 2013 or SharePoint 2016
- Group Expansion REST Service
A separate service from group expansion can be used if:
- It is a REST endpoint that accepts the parameter username.
- The response is an xml with the same format as this one.
- For example, http://call-to-a-different-service:1234/getGroups?username=admin
<groups> <group>tesla</group> <group>scientists</group> <group>italians</group> <group>group1</group> <group>group2</group> <group>group3</group> <group>group4</group> <group>PUBLIC:ALL</group> <group>xxxxxx</group> </groups>
I. Download and uncompress deployment package
- Get the latest deployment package from here.
- Download and uncompress.
II. Configure installation settings
Configure the setup settings in the configurationParameters.xml file located under \Deploy\config.
The Security Trimmer section defines the properties that the Trimmer component needs to access the group expansion service in order to verify the claims of a user requesting documents.
|Group Expansion Service||Url of the Aspire Group Expansion service|
|Group Expansion Timeout||Timeout to wait for Group Expansion response|
|Use Domain||Use domain in security trimmer|
|Claim Issuer||If you are using "Use Aspire" option in the SharePoint2013 Publisher, type "aspire"|
|Search Application Name||Name of the Seach Application|
|Id||The trimmer instance Id in SharePoint. Default is 1.|
|Assembly Version||Version of the trimmer dll registered on the GAC|
|User Profile Web App||Specifies the url of a custom ACL service. Leave empty to use Aspire.|
|Minimum Event Level||Specifies what level of logging should the trimmer use|
III. Run setup script
- Install the Security Pre-Trimmer on all servers hosting a Query Processing component. Check this from SharePoint Central Administration > Manage Service Applications > Search Service Application.
- Make sure all firewalls to the Aspire server are open for the Aspire service port (default: 50505).
From the Deploy\scripts folder, run the corresponding DeployAspireSecurityTrimmer script in a SharePoint Management Shell (run as Administrator):
- To make sure the security trimmer DLL is registered correctly, restart the SharePoint Search Host Controller service.
Consider that default value public for the claimIssuer field in the securityTrimmer section will make all the documents visible. This applies for both configuration files, the main and the one defined for every connector configured for SharePoint.
- Open your preferred internet explorer (IE, Chorme, FireFox, etc) with the "Run as Administrator" option. Otherwise, you will not be able to accomplish the next two steps due to a SharePoint error.
- Go to SharePoint Central Admin > System Settings > Manage Farm Solutions
- Select aspiresecuritytrimmer.wsp and Retract Solution.
- In the following page, make sure the option under Retract When? is set to Now.
Open SharePoint Management Shell as administrator.
A machine and farm administrator user is needed for this.
Go to the Deploy\scripts directory.
Run the following:
To reconfigure the Pre-Trimmer follow the next steps:
1. Retrieve the current settings in the SharePoint Management Shell
2. Remove the Security Pre-Trimmer using the Id from the previous step as Identity by running the following command:
3. Re-register the Security Pre-Trimmer with the necessary changes (i.e. increased timeout)
FAQ & Troubleshooting
Can the Security Pre-Trimmer be Hosted on a Separate Server?
It is not recommended. There are content sources, such as Lotus Notes, that use Intersection ACLs, which requires that Group Expansion is executed in the same server where the content source is.
Security Pre-Trimmer is Never invoked
If there is no activity on the Aspire group expansion servlet when searches are executed, check the SharePoint log files. Look for an exception like:
Debug the Security Pre-Trimmer
Try to initialize the Security Pre-Trimmer manually using PowerShell (make sure to use the correct AspireSecurityTrimmer version in the Add-Type command):
Then, check the content of the error objects:
Check Event Log Permissions
In the windows registry, make sure that the user running the SharePoint Search Host Controller (spsearchhostcontroller) service, has permissions for this key:
Re-Register the Security Pre-Trimmer
Try re-registering the Security Pre-Trimmer. Make sure to restart the SharePoint Search Host Controller (spsearchhostcontroller) service after every configuration change.
Search Not Working At All
If Aspire is not running and the Search Center returns with errors, check the Windows Application log for these error messages:
Internal Server Error
Check Aspire for any error messages or exceptions.
Try to adjust the timeout in the Security Pre-Trimmer configuration. You need to remove and add it again in a SharePoint Management Shell.
Verify That the Trimmer is Installed
- Open the SharePoint 2013 Management Shell
- Run the following command: Get-SPEnterpriseSearchServiceApplication -Identity MySSA | Get-SPEnterpriseSearchSecurityTrimmer
- You should see something like this: