The Group Expansion connector will crawl and expand identities from the Identity Cache
Easy Heading Free | |
---|---|
|
|
|
The Group Expansion connector can crawl and expand identities from the Identity Cache. The Identity Cache is part of the Aspire crawl state database. Typically Elastic Search , Elasticsearch is used as a repository for crawl state database and the Identity Cache is stored in the index aspire-identitycache. The Identity Cache serves works for connectors as a storage for their identities, like groups and users. For example, we can find in the Identity Cache: LDAP users and groups, Confluence users and groups etc in the Identity Cache. The purpose of the Group Expansion Connector is to crawl identities for required seeds, do group expansion and publish the expanded identities. The connector also supports custom mapping configuration for selected seeds.
Let us use this example. If the user : if User1 is part of the group Grp1 and the group Grp1 is part of the group Grp0, then the result of the group expansion is updated information for the user User1. Instead of just having the group Grp1 in the user information, we will have now the list of 2 groups - there: Grp1 , and Grp0 - there. This is what group expansion expanding groups means.
Some seeds require custom mapping for key attribute names. For example, we may need to map a username coming from Confluence connector to the standard AD name. We support two kinds of mapping:
The Group Expansion connector crawls identities from the identity cache. The Identity Cache is part of the Aspire crawl state database. Typically, Elasticsearch is used as a repository for crawl state database and the Identity Cache is stored in the index aspire-identitycache.
Not relevant here
No special requirements here
The File System supports crawling the following the repositories
Info |
---|
This component has been officially tested on local Windows and Linux. |
For the File System connector to be able to crawl the Aspire Worker nodes must be run with an account with read access to the directory to crawl.
The Aspire Worker nodes must be running in the same machine where the file system repository is located or at least have access in the case of a file share.
Name | Supported |
---|---|
Content Crawling | yes |
Identity Crawling | no |
Snapshot-based IncrementalsIncremental s | yes |
Non-snapshot-based IncrementalsIncremental s | no |
Document Hierarchy | yesno |
The File System Group Expansion connector has the following features:
The File System connector is able to Group Expansion connector can crawl the following objects:
Name | Type | Relevant Metadata | Content Fetch & Extraction | Description | |
---|---|---|---|---|---|
FolderSeed | container |
| NA | The directories of the file system. Each directory will be scanned to retrieve more directories or files | |
File | document |
| yes | The files contained by the directories in the crawled file system. |
The File System Connector has the following limitations:
The connector does not retrieve the acls of the crawled documents.identities are grouped by seeds, and we crawl identities belonging to seeds | ||||
Identity |
| NA | The identities with expanded groups |
No limitations defined