Security TrimmingQuery pipeline stage configuration specifications
This stage is deprecated in Managed Fusion 5.9.0. The Graph Security Trimming stage, introduced in Managed Fusion 5.6.0, uses a single filter query for all data sources instead of one filter query per data source. Migrate your query pipeline stage to the graph security trimming stage. |
The Security Trimming query pipeline stage restricts query results according to the user ID. While indexing the content, the Managed Fusion connectors service stores security ACL metadata associated with the crawled items and indexes them as fields. The Security Trimming stage matches this information against the ID of the user running the search query.
This stage supports asynchronous processing.
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.
|