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 ConnectivityHub 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 domain users and groups or native security
Required Software .NET Framework v4.7.2

IIS 

  • Egnyte requires oAuth 2.0 Standard authentication
  • oAuth authentication requires your Egnyte Connector site in IIS be run with HTTPS

Certificates

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 with creating Self-Signed Certificates. 

If you decide to use the built-in tools to create a self-signed certificate when installing the connector, then 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 crawl Egnyte content efficiently these numbers must be increased. 

Contact your Egnyte representitive to increase the values of these settings.