Egnyte Connector Prerequisites
The following tables details the requirements that must be satisfied to use the Egnyte connector
User Accounts and Application Permissions
| Required Permission | Description |
|---|---|
| Egnyte User Account |
Admin user account to access with access to all content to be indexed |
| Custom Security | Custom security can be set within the Connector Framework or Connectivity Hub based on business rules. |
Connector Features and Requirements
| Features | Supported | Additional Information |
|---|---|---|
| Searchable Content Types | Yes | All content types. |
| Content Update | Full and Incremental | All BA Insight Connectors support both Full and Incremental crawls, unless noted. |
| Permission Types | Yes | The content can be secured via Active Directory A directory service for Windows domain networks. A hierarchical structure that stores information about objects on the network. Used to manage permissions and control access to critical network resources. domain users and groups or native security |
| Required Software | .NET Framework v4.7.2 |
|
Egnyte Connector in IIS
- Egnyte requires OAuth Specifies a process for resource owners to authorize third-party access to their server resources without providing credentials. 2.0 Standard authentication.
- OAuth authentication requires that the Egnyte Connector IIS site is run with HTTPS.
Certificate Requirement
A domain certificate or a self-signed high trust certificate is required to bind the Egnyte IIS site to HTTPS.
Note: The Egnyte Connector has tools which can help you create a Self-Signed Certificates. If you decide to use the built-in tools to create a self-signed certificate when installing the connector, you must use a service account with local admin permissions.
Application
Before you can use the Egnyte Connector, the end user must have a registered application account. With the application, you are assigned a private key and secret which is used to access the content to be indexed. For OAuth, the application requires a redirect page in the following format:
- https://<yourfinalhostname>/oAuth.aspx
Performance
When initially provisioned, Egnyte applications have the following default settings:
- QPS (Queries per Second): 2
- Daily call limit: 1000 calls
To help you calculate the appropriate number of API calls to request, refer to the following list to see how the connector consumer API calls:
-
2 calls per document indexed
-
1 call per folder traversed
-
1 call per 100 users, group, or group member enumerated