Egnyte
On This Page
Overview
The Egnyte connector in DryvIQ allows you to analyze, migrate, copy, and synchronize files to/from your Egnyte account to/from cloud storage repositories and on-premise network file shares. The first step is to create the Egnyte connection by providing the connection information required for DryvIQ to connect to the account.Â
Creating a Connection
Expand the Manage section in the left navigation menu.
Click Connections.
Click Add connection.
Select Egnyte as the platform on the Add connection modal.
Enter the connection information. Reference the table below for details about each field.
Click Sign in with Egnyte.
On the Egnyte log in modal, enter the e-mail address or username for the account you are using for the connection and click Continue.
Enter the password for the account and click Log in.Â
Click Allow Access when prompted to authorize the connection.
You will see a green "Connected” message on the bottom of the modal when DryvIQ establishes connection. (If the connection fails, verify the information you entered.)
Click Done to finish creating the connection.Â
Add Connection Modal for Egnyte
Â
Field | Description | Required |
---|---|---|
Display as   | Enter the display name for the connection. If you will be creating multiple connections, ensure the name readily identifies the connection. The name displays in the application, and you can use it to search for the connection and filter lists. If you do not add a display name, the connection will automatically be named using the account owner's name. For example, Egnyte (John Doe). If it will be useful for you to reference the connection by account, you should use the default name. | Optional |
User Type | Required | |
Connect as standard user | Select this option to create a standard connection to access a user's files and folders. This is the default selection. | Â |
Connect as account administrator | Select this option to create an administrator connection. This requires administrator privileges and grants access to all accounts within the organization. This option is often used along with impersonation to simplify transferring multiple user accounts. When connected as an administrator, the first level of folders will be user names. |  |
Domain | Enter the URL for your Egnyte account. It will look something like https://companyname.egnyte.com. | Required |
Â
Egnyte Log InÂ
Â
Â
Grant Access to Egnyte Account
Features and Limitations
Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms and allows you to configure actions based on Job Policies and Behaviors. Use the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations.Â
Supported Features | Unsupported Features | Other Features/Limitations |
---|---|---|
Invalid characters: / < > : \ | ? * + | ||
Timestamp preservation | Path length maximum | |
Segment path length: 245 | ||
No leading periods | ||
No trailing periods before extensions | ||
Permission preservation | Â | No leading whitespace |
 | No trailing whitespace before an extension | |
 | No trailing whitespace after an extension | |
 |  | No non-printable characters |
API Rate Limits
Depending on the project scope, performance may be impacted by Egnyte's rate-limiting restrictions. Prior to transferring content, DryvIQ recommends contacting Egynte (api-support@egnyte.com) to discuss increasing your API call volume by obtaining additional OAuth tokens. Requesting additional OAuth tokens will allow DryvIQ to make the required calls to Egnyte while working within their restrictions. The performance will depend on the number of additional OAuth tokens approved by Egnyte for your tenant. Please see Egnyte's documentation for further details.
Path Lengths
Egnyte does not impose restrictions for the total path length.
Segment path lengths are limited to 245 character. Segments are delimited by a forward slash (/). For example, <max 245 characters>/<max 245 characters>.
Permissions
DryvIQ supports and migrates permissions if “Permissions Inheritance” is enabled on Egnyte.
Timestamp Preservation
The DryvIQ Platform will extract and preserve file timestamps for created-on and modified-on dates for all storage platforms. However, Egnyte does not maintain a traditional created-on timestamp. When the source platform does not preserve the created-on timestamp, DryvIQ will make all attempts to capture timestamps starting with Egnyte's modified-on timestamp.
For the Version Preservation feature, DryvIQ is using two variants of Egnyte's modified-on timestamp:
Modified-on First Version: This is the closest parallel to a traditional created-on timestamp. For the first version of the file, regardless of how many versions exist, the first modified-on timestamp is considered the created-on timestamp.
Modified-on Current Version: This is the closest parallel to last modified-on timestamp. For the current version of the file, the modified-on timestamp is considered the last modified-on timestamp.
While the Egnyte uploaded-on timestamp is available, DryvIQ ignores this option as there is no corresponding timestamp attribute available on other storage platform. For example, Box's uploaded-on timestamp is a native operation, and Box prevents any write operation to this attribute.
Users
Egnyte supports three levels of users: Administrators, Power Users, and Standard Users. DryvIQ handles each user differently. For more information about Egnyte users, refer to Egnyte's Users and Groups documentation.
Administrators: This is the user who registers for the account. That user is automatically set as the account administrator.
Power Users: These users are the company employees. These are considered internal users. Author preservation is preserved for content created in private folders and for Egnyte Power Users. Sharing permissions are also preserved for power users.
Standard Users: These are the company’s business partners. These are considered external users. If standard users are included in a group, they are not transferred, and DryvIQ will not log unresolved permission errors.
Â