Restrictions

The following is a list of the restrictions with the Syncplicty connector.

1. The maximum length of any folder or file name is 260.

2. No leading or trailing spaces in folder names, file names, or file extensions.

3. Restricted characters in the file name: < > : / \ " ' | ? * . [ ] { } ( ) ! ;

Installation

This a cloud service provider but they do have the concept of "Storage Vaults". These data repositories can be hosted in the cloud or on premises.

– Syncplicity has the concept of storage vaults where the content is physically or virtually stored. Each Sync Point must be associated with a specific Storage vault and one storage vault can be set as the default for all new sync points by Syncplicity. There is no visibility for this with SkySync and is managed within the Syncplicity account.

API Method

Our connection to Syncplicity uses a Rest API

Authentication

Our Syncplicity connection uses Oauth 2.0 with some special features.

1. Client credentials grant type.

2. There is a special authentication method written to connect to the storage vaults.

Special Notes

Additional information on other limitations regarding Syncplicity

Expand for more information

Syncplicity has some aggressive rate limitations in place.

1. This limitations can not be adjust by the user and they would need to contact Syncplicity.

2. These rate limitations are determined by app key and app secret entered so if multiple instances are setup using that same set of credentials they share the limitation.

Sync Points - Root folders on a Syncplicity connector is known as a sync points and they have a special relationship to storage vaults and permissions.

1. Any folder off of the account root is a sync point. Each Sync point can be assigned to a storage vault in the native interface. For newly created root folders there is a default sync point.

2. Wtihin SkySync there is no way to see what Storage Vault a sync point has been assigned.

3. Permissions only exist on sync points and do not extend int the nested paths. When doing a permissions migration into Syncplicity only the sync points can be set.

User Permissions

1. Any New user accounts need to be enable to use the API. It can be requested under the specific account but it requires a second account to authorize access.

2.We recommend that you do not increase parallel writes above 6 parallel writes

3. User Drive Mapping
- There is no way to get a user list if it is selected as a source

Permissions – Syncplicity support permission migrations but only for the sync points. When creating a permissions migration job from a connector that supports the full range of permissions the job will only migrate the permissions for the root sync points in Syncplicity.

User Drive Mapping – Unlike some other connectors Syncplicity does not show the list of users attached to the enterprise account. You need to externally assemble the list of users to either create a user map or to impersonate a specific user/

Connector : Syncplicity

Restrictions

The following is a list of the restrictions with the Syncplicty connector.

1. The maximum length of any folder or file name is 260.

2. No leading or trailing spaces in folder names, file names, or file extensions.

3. Restricted characters in the file name: < > : / \ " ' | ? * . [ ] { } ( ) ! ;

Installation

This a cloud service provider but they do have the concept of "Storage Vaults". These data repositories can be hosted in the cloud or on premises.

API Method

Our connection to Syncplicity uses a Rest API

Authentication

Our Syncplicity connection uses Oauth 2.0 with some special features.

1. Client credentials grant type.

2. There is a special authentication method written to connect to the storage vaults.

Special Notes

Additional information on other limitations regarding Syncplicity

Syncplicity has some aggressive rate limitations in place.

1. This limitations can not be adjust by the user and they would need to contact Syncplicity.

2. These rate limitations are determined by app key and app secret entered so if multiple instances are setup using that same set of credentials they share the limitation.

Sync Points - Root folders on a Syncplicity connector is known as a sync points and they have a special relationship to storage vaults and permissions.

1. Any folder off of the account root is a sync point. Each Sync point can be assigned to a storage vault in the native interface. For newly created root folders there is a default sync point.

2. Wtihin SkySync there is no way to see what Storage Vault a sync point has been assigned.

3. Permissions only exist on sync points and do not extend int the nested paths. When doing a permissions migration into Syncplicity only the sync points can be set.

User Permissions

1. Any New user accounts need to be enable to use the API. It can be requested under the specific account but it requires a second account to authorize access.

2.We recommend that you do not increase parallel writes above 6 parallel writes

3. User Drive Mapping- There is no way to get a user list if it is selected as a source

Permissions – Syncplicity support permission migrations but only for the sync points. When creating a permissions migration job from a connector that supports the full range of permissions the job will only migrate the permissions for the root sync points in Syncplicity.

User Drive Mapping – Unlike some other connectors Syncplicity does not show the list of users attached to the enterprise account. You need to externally assemble the list of users to either create a user map or to impersonate a specific user/

3. User Drive Mapping
- There is no way to get a user list if it is selected as a source