Dropbox Connector

Installation and Configuration

Mindbreeze GmbH, A-4020 Linz, 2020.

These documents are strictly confidential. The submission and presentation of these documents does not confer any rights to our software, our services and service outcomes, or any other protected rights. The dissemination, publication, or reproduction hereof is prohibited.

For ease of readability, gender differentiation has been waived. Corresponding terms and definitions apply within the meaning and intent of the equal treatment principle for both sexes.

Installation

Before installing the Dropbox Online connector, make sure that the Mindbreeze server is installed and the Dropbox connector is included in the license. Use the Mindbreeze Management Center to install or update the connector.

Plugin installation via Mindbreeze Management Center

To install the plug-in, open the Mindbreeze Management Center. Select “Configuration” from the menu pane on the left-hand side. Then navigate to the “Plugins” tab. Under “Plugin Management,” select the appropriate zip file and upload it by clicking “Upload.” This automatically installs or updates the connector, as the case may be. In the process, the Mindbreeze services are restarted.

Configuring Mindbreeze

Configuration of the index

Navigate to the "Indices" tab and click on the "Add new index" icon in the upper right corner to create a new index. Select Dropbox as the data source.

If necessary, change the display name.

Configuration of the data source

Scroll down to the Data Sources tab. There you can configure the data source according to your needs.

Section „Dropbox Settings“

In the "Dropbox Settings" section you can define your dropbox installation to be indexed. The following options are available:

„Admin Email Address“	The email address of the admin user with which the dropbox should be crawled. Only documents to which this admin user has access can be indexed.
„API Key Credential“	You must create a Password Credential in the Network tab, where you enter your API key as the password. This credential must then be selected here. How to get the API key from Dropbox is explained in a later chapter.
„Maximum Page Size“	Block size of a metadata request
„Parallel Request Count“	Maximum number of HTTP requests that are sent simultaneously
„Connection Timeout“	Time in seconds to wait for a response before the API call is aborted
„File Size Limit“	Maximum size of the files to be downloaded in MB. Files larger than the specified value will not be downloaded or indexed.
“Team Folder Include Pattern (regex)”	Regular Expression, which indicates which team folders should be crawled.
“Folder Include Pattern (regex)”	Regular Expression, which specifies which regular folders should be crawled.
“Team Folder Select Pattern"	Regular Expression, which specifies for which Team Folders the Folder Include Pattern should be applied.
”Use Server Modified Date for Deltacrawl”(Advanced Setting)	This option should no longer be changed.

Getting the API key from Dropbox

Go to https://www.dropbox.com/developers/apps and use the "Create App" button to create a new app.

This app needs access to the "Dropbox Business API" and the required access type is "Team member file access". Then you can still name your app. With the "Create app" button the app will be created.

After you have created your app, you can have an API key generated in the App Settings. This is then used for the Password Credential.

Configuration of the Principal Resolution Service

Select "Advanced Settings" to make the following settings.

Activate the "Enforce ACL Evaluation" option in the index, if it is not already activated.

Add a new service in the "Services" area by clicking on "Add Service". Select "Dropbox Principal Resolution Cache" and assign a display name.

Section „Connection Settings“

Enter the information about your Dropbox installation in the "Connection Settings" section. For "Admin Email Address" and "API Key Credential" you can simply make the same entries as in the crawler. The advanced option "HTTP Dumping Path" is a debug option, where all HTTP requests and responses are stored on the specified path. This should not be configured in production operation.