Set up a Dropbox connector
Capabilities
Resource | Sync | Provision |
---|---|---|
Accounts | ✅ | |
Roles | ✅ | ✅ |
Groups | ✅ | ✅ |
Gather Dropbox credentials (self-hosted only)
If you’re setting up a cloud-hosted Dropbox connector, which authenticates using OAuth, you can skip this section. Configuring the self-hosted connector requires you to pass in credentials for Dropbox. Gather these credentials before you move on.
A user with access to the Dropbox developer platform must perform this task.
Create a Dropbox app
Navigate to the Dropbox developer platform and click App Console > Create app.
Follow the prompts to create a new app.
Click Create app. On the app’s details page, carefully copy and save the app’s key and secret.
On the Permissions tab, enable Team Scopes.
Get a Dropbox refresh token
First, run the following to get a short-lived access code for the Dropbox API, pasting in your app’s key:
https://www.dropbox.com/oauth2/authorize?client_id=<APP_KEY>&token_access_type=offline&response_type=code
Then, run the following, pasting in the access code along with your app’s key and secret, to generate a refresh token:
curl --location --request POST 'https://api.dropboxapi.com/oauth2/token' \ -u '<APP_KEY>:<APP_SECRET>' -H 'Content-Type: application/x-www-form-urlencoded' \ --data-urlencode 'code=<ACCESS_CODE>' \ --data-urlencode 'grant_type=authorization_code'
Carefully copy and save the refresh token.
That’s it! Next, move on to the self-hosted connector configuration instructions.
Configure the Dropbox connector
To complete this task, you’ll need:
- The Connector Administrator or Super Administrator role in ConductorOne
- The Admin role in Dropbox
Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.
In ConductorOne, navigate to Admin > Connectors and click Add connector.
Search for Dropbox and click Add.
Don’t see the Dropbox connector? Reach out to support@conductorone.com to add Dropbox to your Connectors page.
Choose how to set up the new Dropbox connector:
Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
Find the Settings area of the page and click Edit.
Click Login with OAuth.
Log in and authorize ConductorOne with your Dropbox instance.
After authorizing, you’ll be redirected back to the ConductorOne integrations page, where an “Authorized as” message is now printed.
Click Save.
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
That’s it! Your Dropbox connector is now pulling access data into ConductorOne.
Follow these instructions to use the Dropbox connector, hosted and run in your own environment.
When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.
Step 1: Set up a new Dropbox connector
In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new Dropbox connector:
Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
Click Next.
In the Settings area of the page, click Edit.
Click Rotate to generate a new Client ID and Secret.
Carefully copy and save these credentials. We’ll use them in Step 2.
Step 2: Create Kubernetes configuration files
Create two Kubernetes manifest files for your Dropbox connector deployment:
Secrets configuration
# baton-dropbox-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
name: baton-dropbox-secrets
type: Opaque
stringData:
# ConductorOne credentials
BATON_CLIENT_ID: <ConductorOne client ID>
BATON_CLIENT_SECRET: <ConductorOne client secret>
# Dropbox credentials
BATON_APP_KEY: <Dropbox app key>
BATON_APP_SECRET: <Dropbox app secret>
BATON_REFRESH_TOKEN: <Dropbox refresh token>
See the connector’s README or run --help
to see all available configuration flags and environment variables.
Deployment configuration
# baton-dropbox.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: baton-dropbox
labels:
app: baton-dropbox
spec:
selector:
matchLabels:
app: baton-dropbox
template:
metadata:
labels:
app: baton-dropbox
baton: true
baton-app: dropbox
spec:
containers:
- name: baton-dropbox
image: ghcr.io/conductorone/baton-dropbox:latest
imagePullPolicy: IfNotPresent
envFrom:
- secretRef:
name: baton-dropbox-secrets
Step 3: Deploy the connector
Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the Dropbox connector to. Dropbox data should be found on the Entitlements and Accounts tabs.
That’s it! Your Dropbox connector is now pulling access data into ConductorOne.