Skip to main content
  • Latest version: v2.0.0
  • Compatible with Fusion version: 5.9.4 and later
The v2.0.0 version of this connector is only compatible with Fusion 5.9.4 and later when using security trimming. The v2.0.0 connector version uses Graph Security Trimming and not regular security trimming. It is imperative to treat this as a new connector, as configurations do not transfer over due to disparities between newer versions and previous ones. A full crawl is mandatory.

​
Security trimming

The Windows Share SMB V2 connector supports graph security trimming. If you are using Fusion 5.18.0 or later, you can use separate collections to store your content and your ACLs. Use a separate sidecar collection if you need to manage ACL data independently of the rest of your content. To use a sidecar collection for your ACLs, you must create the ACL collection before configuring your datasource to read from this collection. To enable graph security trimming for your datasource:
  1. Navigate to Indexing > Datasources.
  2. Open your datasource.
  3. Under Graph Security Filtering Configuration, select Enable security trimming.
  4. If you are using a sidecar collection in Fusion 5.18.0 or later, set ACL Collection ID to your ACL collection name (for example, acl_collection).
  5. Save your changes.
After configuring your datasource, you must reference the ACL collection in the Graph Security Trimming stage.
If you are transitioning from using the same collection to creating a sidecar collection for ACLs, you must run a full recrawl of your datasource so the ACLs route to the sidecar collection. ACL documents stored in the content collection from before the migration remain in the content collection unless the collection is reindexed or manually cleaned.

​
Remote connectors

V2 connectors support running remotely in Fusion versions 5.7.1 and later. For more information, see Configure remote V2 connectors. Below is an example configuration showing how to specify the file system to index under the connector-plugins entry in your values.yaml file:
You may also need to specify the user that is authorized to access the file system, as in this example:

​
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.