DropBox for Business
On This Page
- 1 Overview
- 2 Create Connection | User Interface
- 3 Features and Limitations
- 3.1 Files and Folders
- 3.1.1 Author Preservation
- 3.1.2 Business Team Folders
- 3.1.3 Character Sanitization
- 3.1.4 Dropbox Paper
- 3.1.5 Path Lengths
- 3.1.6 Rate Limits in Containerized Environments
- 3.1.7 Shared Links
- 3.1.8 Versioning
- 3.1.9 Version Limits
- 3.2 Create Connection | REST API
- 3.3 Create Job | Dropbox for Business Account Admin Connection
- 3.4 Transferring Dropbox for Business Team Folders
- 3.1 Files and Folders
Overview
The Dropbox connector in DryvIQ allows you to analyze, migrate, copy, and synchronize files to your Dropbox account from cloud storage repositories and on-premise network file shares. The first step is to create the Dropbox connection by providing the connection information required for DryvIQ to connect to the server. The connector can be created using a standard Dropbox account or a Dropbox for Business account. However, when creating a connection using a Dropbox for Business account, you must use an Administrator account. Standard accounts will return an error from the Dropbox for Business platform.
For more information on using a standard Dropbox account, please refer to the Dropbox connector page.
Create Connection | User Interface
Select Connections > Add connection.
Select Dropbox for Business as the platform on the Add connection modal.
Enter the connection information. Reference the table below for details about each field.
Select Sign in with Dropbox for Business.
On the Dropbox API Request Authorization modal, enter the Email and Password required to log in to the account and select Sign In. Only an Administrator account can be used for Dropbox for Business. Standard accounts will return an error from the Dropbox for Business platform.
Select Allow when prompted to authorize the connection.
You will see a "Connection test succeeded" message on the Add connection modal. (If you don't see this message, repeat the sign in and authorization steps above.)
Select Done to finish creating the connection.
Add Connection Modal - Dropbox for Business
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, "Dropbox for Business." DryvIQ recommends that you edit the name to more readily identify the connection. | Optional |
Platform API client credentials | Required | |
Use the system default client credentials | Select this option to use the default DryvIQ client application. |
|
Use custom client credentials | Select this option to use custom client credentials provided by your administrator. When selected, two additional fields will be available to enter the credentials. |
|
Client ID | This field displays only when you select Use custom client credentials. This value will be provided by your administrator. | Required when using custom credentials |
Client Secret | This field displays only when you select Use custom client credentials. This value will be provided by your administrator. | Required when using custom credentials |
Include unmounted folders | Indicate if you want to DryvIQ to show unmounted folders owned by the user. The default option is No, so unmounted folders do not display. If you select Yes, DryvIQ will display unmounted folders owned by the user. Only folders will display; the contents for the folders will not display. DryvIQ will not migrate the unmounted folders if used in a job. The DryvIQ will be slow to return folders when you include unmounted folders due to the response times of the Dropbox API required to obtain this information. | Optional |
Dropbox API Request Authorization modal
Allow Access to Dropbox
Connection Test Succeeded
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. Utilize the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations.
Files and Folders
Below is list of Dropbox's supported and unsupported features as well as additional file/folder restrictions.
Supported | Unsupported | Other Features/Limitations |
---|---|---|
(See Versioning below.) | < > \\ / : ? * \ | ~ | |
File size maximum: 50 GB or smaller | ||
Path length maximum: n/a | ||
Segment path length: 255 | ||
| Maximum number of files per folder: 10,000 | |
| No trailing spaces after file extensions | |
|
| |
|
|
Author Preservation
The Dropbox connector uses "per-request impersonation." This means DryvIQ makes requests to the platform on behalf of the account owner, not the administrator. Therefore, files created by other users will fail to upload unless the account owner mounts the shared parent folder into their Dropbox drive before uploading the file. (See https://help.dropbox.com/files-folders/add-shared-folder for more information.) Failed uploads will be logged with a message similar to the following example: "[PermissionFailure] The account 'Joe Smith' is not authorized to perform the requested operation."
Missing or unknown account in Dropbox
If a job is set to impersonate an invalid or unknown Dropbox user during author preservation, DryvIQ will log an error in the Job Activity report. You will see an “Unknown failure” in the job activity with an error description that reads, “Missing or unknown account in Dropbox: <email address>” (where <email address> will be the invalid account that was encountered).
Business Team Folders
Team folders transfer automatically with any transfer job; however, Team and Shared folders must first be mounted in Dropbox (Dropbox for Business API only surfaces mounted Team and Shared folders). If you include Job Filters | Filter Shared Content, Team Folders will not be transferred. The Dropbox for Business connector creates shared user folders by default. To create shared folders in a Team Folder, the root Team Folder must be created in the Dropbox UI and selected as the root of the job. Shared folders that are created in a Team Folder support permission disinheritance. Shared folders created in a user folder do not support disinheritance and will log a warning.
Character Sanitization
DryvIQ will sanitize file names that contain combined Unicode characters by replacing the characters with an underscore (_).
Dropbox Paper
DryvIQ does not support Dropbox paper. Dropbox Paper is a separate work space that stores Paper documents in your account on http://paper.dropbox.com . DryvIQ doesn't support have access to these documents as part of your Dropbox connection.
Path Lengths
Dropbox does not impose restrictions for the total path length.
Segment path lengths are limited to 255 character. Segments are delimited by a forward slash (/). For example, <max 255 characters>/<max 255 characters>.
Rate Limits in Containerized Environments
The Dropbox for Business API organizes content into namespaces, which can represent a user's home folder (their personal namespace ID), a shared folder, or a team folder within a team space. The API enforces limits on concurrent operations within a namespace and will return a too_many_write_operations
error if these limits are exceeded. The DryvIQ Dropbox for Business connector adheres to Dropbox's best practices to minimize the likelihood of hitting these rate limits. However, in a containerized environment (or across multiple nodes), it is important to avoid running folder mapping jobs or multiple concurrent operations within the same namespace. (For example, avoid mapping folders into subfolders of a user's drive.) The locking mechanism used to prevent concurrent operations does not function across containers, which could lead to higher instances of rate limit errors.
Shared Links
Editor access is preserved for shared links on containers only in Dropbox; shared links for files only support viewer access.
Versioning
The Dropbox platform treats content version history differently than other cloud platforms, with each native move and rename tracked as a new version. In order to only transfer true version history, enable the Scripting option on step 6 during job creation and copy the following JSON into the scripting box:
{
"transfer": {
"versioning": {
"preserve": "native",
"select": "published"
}
}
}
For more information about how to use Advanced Scripting, refer to the Advanced Scripting | Additional Configuration Options page.
Version Limits
While Dropbox allows you to store unlimited versions, the platform restricts version downloads to 100. This means only the most recent 100 versions for a given file will be transferred to the destination. Refer to the Dropbox API Documentation for more information. You can also find additional information in the Dropbox Forum.
Create Connection | REST API
Create a New Dropbox for Business Connection
The following GET will return a target URL. Use this URL to log in to the Dropbox for Business account to authenticate and create the connection. Make sure you connect using an Administrator account.
GET {{url}}v1/connections/platforms/dfb/new
Create a New Dropbox for Business Connection Using Custom Credentials
Create a new connection using custom credentials with the example call below. Replace the name, client_id, and client_secret with information relevant to your connection.
{
"name": "Dropbox for Business",
"platform": {
"id": "dfb"
},
"auth": {
"client_id": "{{clientID}}",
"client_secret": "{{clientSecret}}"
}
}
Dropbox for Business with Single Sign-On (SSO)
Create a new connection using single sign-on with the example call below. You will need to obtain the applicable access token for your Dropbox for Business account.
Create Job | Dropbox for Business Account Admin Connection
Create a simple transfer job using the example call below. Replace the information with information relevant to your job and connectors.
Transferring Dropbox for Business Team Folders
Team folders will transfer automatically with any transfer job; however, Team and Shared folders must first be mounted in Dropbox (Dropbox for Business API only surfaces mounted Team and Shared folders)
If you include Job Filters | Filter Shared Content, Team Folders will not be transferred.
The Dropbox for Business connector creates shared user folders by default. To create shared folders in a Team Folder, the root Team Folder must be created in the Dropbox UI and selected as the root of the job.
Shared folders that are created in a Team Folder support permission disinheritance. Shared folders created in a user folder do not support disinheritance and will log a warning.