On This Page
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-premise 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. In order to create a connection from DryvIQ to Syncplicity, you will need to complete configuration on the Syncplicity side, and you will need to provide several pieces of authentication information. Refer to the Syncplicity API Portal for 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 needs to be used.
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 on the bottom of the modal when DryvIQ establishes connection. (If the connection fails, verify the information you entered.)
If the connection uses SVA, proceed to Sign in With SVA. Otherwise, click Done to finish creating the connection.
Add Connection Modal for Syncplicity
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 in 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. | |
Application token | This value is provided by your Syncplicity administrator. 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 OAuth 2.0 client credentials grant. You should protect this token. Refer to the Syncplicity API Portal Documentation to more. | Required |
App key | This value is provided by your Syncplicity administrator. 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 Documentation to more. | Required |
App secret | This value is provided by your Syncplicity administrator. 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 Documentation to more. | Required |
Behavior When Deleting Items | Select the type of delete DryvIQ should perform when deleting items: Permanent or Soft. Soft delete is the default delete behavior; however, Permanent is the recommended behavior. A soft delete marks items as a deleted. You can still access them to restore or permanently delete the items. A permanent delete removes the items. This delete 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 type 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 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 needs to be used 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 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.
Syncplicity OneLogin Modal
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 |
|---|---|---|
Path length maximum: n/a | ||
Segment path length: 260 | ||
No leading spaces in file name/folder names | ||
No trailing spaces before or after file extensions | ||
No non-printable ASCII characters | ||
Invalid characters: \ / < > | ||
Only syncpoints can be shared with other users and have permissions persist. | ||
Users with a large number of syncpoints are not supported by Syncplicity. |
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 the files and folders can be transferred.
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.
Trailing whitespace before the file extension will also be replaced by an underscore.
Path Lengths
Syncplicity does not impose restrictions for the total path length.
Segment path lengths are limited to 260character. Segments are delimited by a forward slash (/). For example, <max 260 characters>/<max 260 characters>.