Overview
The Syncplicity connector in DryvIQ allows you to analyze, migrate, copy, and synchronize files to your Syncplicity service from cloud storage repositories and on-premises network file shares. The first step is to create the Syncplicity connection by providing the connection information required for DryvIQ to connect to the platform. DryvIQ connections to Syncplicity require OAuth 2.0 access. To make a connection from DryvIQ to Syncplicity, you must complete the configuration on the Syncplicity side and provide several pieces of authentication information. Refer to the Syncplicity API Portal to learn more.
Syncplicity supports storage vault authentication (SVA), which provides an additional layer of security. The feature is optional and needs to be enabled in the storage connector services in Syncplicity. When enabled, the connector services require both an Open Authentication 2.0 (OAuth 2.0) access token and user authentication. If you create a connector for a Syncplicity connection with SVA enabled, you will need to complete additional steps to provide the user authentication that is required.
Creating a Connection
- Expand the Manage section in the left navigation menu.
- Click Connections.
- Click Add connection.
- Select Syncplicity as the platform on the Add connection modal.
- Enter the connection information. Reference the table below for details about each field.
- Click Test connection to ensure DryvIQ can connect using the information entered.
- You will see a green "Connected” message at the bottom of the modal when DryvIQ establishes a connection. (If the connection fails, verify the information you entered.)
- If the connection uses SVA, click Sign in With SVA. (refer to the “Sign in With SVA” section below for more information.) Otherwise, click Done to finish creating the connection.
| 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, Syncplicity (John Doe). If you need to reference the connection by account, 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. | |
| Application token | Your Syncplicity administrator provides this value. Each user can provision a personal application token, which can be used to authenticate in UI-less scenarios via API. This is useful for account administration tasks that run in a headless session. If provisioned, an application token is the only information required to log in a user using the OAuth 2.0 client credentials grant. You should protect this token. Refer to the Syncplicity API Portal for more information. | Required |
| App key | Your Syncplicity administrator provides this value. The application key identifies DryvIQ (the third-party application) as defined by OAuth 2.0. DryvIQ uses the application key and application secret to authenticate with Syncplicity. Refer to the Syncplicity API Portal for more information. | Required |
| App secret | Your Syncplicity administrator provides this value. The application secret serves as the password for the connection as defined by OAuth 2.0. DryvIQ uses the application key and application secret to authenticate with Syncplicity. Refer to the Syncplicity API Portal for more information. | Required |
| Behavior When Deleting Items |
Select the type of deletion DryvIQ should perform when deleting items: Permanent or Soft.
Soft delete is the default behavior. A soft delete marks items as deleted. You can still access them to restore or permanently delete the items.
Permanent delete is the recommended behavior. A permanent delete removes the items. This deletion is not reversible. |
Optional |
| New SyncPoint type | Select the syncpoint type for the list: Standard Sync Folder or SyncDrive Folder. This option instructs DryvIQ as to the kind of folder that should be created when a top-level folder is created through a DryvIQ process. Refer to SyncDrive for Windows Users to learn more about these options.. | Optional |
Sign in With SVA
Once DryvIQ establishes a connection, it will display an additional sign-in option for accounts that have storage vault authentication enabled. You must complete the extra sign-in step to provide the user authentication that is needed for the connection to access the storage vault. If there are multiple storage vaults enabled for the account, you will see a button for each storage vault. If you want to access multiple storage vaults, you must complete the sign-in steps for each vault. Similarly, you don't have to sign into a storage vault if you don't want the connector to use it.
- Click Sign in with. (The name of the button will reflect the name of the storage vault it is accessing.)
- A Syncplicity OneLogin modal appears.
- Enter the username for the account and click Continue.
- Enter the password for the account and click Continue.
- You will see an "SVA sign in succeeded" message when DryvIQ establishes a connection. (If you don't see this message, verify the information you entered.)
- If there are multiple storage vaults, repeat these steps for each storage vault the connector needs to access.
- Select Done to finish creating the connection.
Features and Limitations
Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms, allowing you to configure actions based on Job Policies and Behaviors. The information below is platform-specific. Use the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations.
| Supported Features | Unsupported Features | Other Features/Limitations |
|---|---|---|
| Version Preservation | File Lock Propagation |
Path Length Maximum: N/A See below for more information. |
| Timestamp Preservation | Mirror Lock Ownership |
Segment Path Length: 260 See below for more information. |
| Author/Owner Preservation | File Size Maximum |
Invalid Characters : \ / < > See below for more information. |
| Account Map | Restricted Types | No leading spaces in file name/folder names See below for more information. |
| Group Map | Metadata Map | No trailing spaces before or after file extensions |
| Permission Preservation | Tags Map | No non-printable ASCII characters |
| User Impersonation |
|
Only syncpoints can be shared with other users and have permissions persist. |
| Syncplicity does not support users with a large number of syncpoints. |
Too Many Syncpoints
If you are creating a new impersonation job with a Syncplicity connection and the source or destination location is empty, the user you are impersonating has too many syncpoints. You will need to delete the syncpoints before you can create the job.
Invalid Characters and Spaces
DryvIQ verifies file and folder names to identify unsupported characters based on the platform. It then replaces invalid characters with an underscore (_) so it can transfer the files and folders.
The logic includes leading and trailing spaces in file and folder names. DryvIQ replaces the space rather than trimming it because trimming the space could cause duplicate file names. Adding the underscore ensures the name remains unique.
DryvIQ replaces trailing whitespace before the file extension with an underscore.
Path Lengths
Syncplicity does not impose restrictions on the total path length. However, segment path lengths are limited to 260 characters. Segments are delimited by a forward slash (/). For example, <max 260 characters>/<max 260 characters>.