Graph Security Trimming Stage
The Graph Security Trimming stage restricts query results according to the user ID as an alternative to Security Trimming Stage. Whereas the Security Trimming stage has one Solr filter query per data source, Graph Security Trimming uses a single filter query for all data sources.
Stage setup
When using this stage with SharePoint Optimized V2 or LDAP ACLs V2 connectors, configure the following settings:
| Field | Value |
|---|---|
ACL solr collection |
|
User ID source |
|
User ID key |
The key that contains the User ID |
Join method |
|
Join Field |
|
| Refer to Configure Security Trimming for SharePoint Optimized V2 and Migrate to Graph Security Trimming in Fusion 5.8 or later for more information. |
|
Lucidworks offers free training to help you get started. The Quick Learning for Configuring Graph Security Trimming focuses on how to set up security trimming:
Visit the LucidAcademy to see the full training catalog. |
Query pipeline stage condition examples
Stages can be triggered conditionally when a script in the Condition field evaluates to true. Some examples are shown below.
Run this stage only for mobile clients:
params.deviceType === "mobile"Run this stage when debugging is enabled:
params.debug === "true"Run this stage when the query includes a specific term:
params.q && params.q.includes("sale")Run this stage when multiple conditions are met:
request.hasParam("fusion-user-name") && request.getFirstParam("fusion-user-name").equals("SuperUser");
!request.hasParam("isFusionPluginQuery")The first condition checks that the request parameter "fusion-user-name" is present and has the value "SuperUser". The second condition checks that the request parameter "isFusionPluginQuery" is not present.
Configuration
When entering configuration values in the UI, use unescaped characters, such as \t for the tab character. When entering configuration values in the API, use escaped characters, such as \\t for the tab character.
|