The Tridion Connector for Dropbox provides access to assets stored in Dropbox, like images, documents, videos and more. With this connector, you can build websites using the Dropbox assets, and then share this content across the whole organization. Please find the documentation link for more details.
The Connector for Dropbox provides the following key capabilities:
- List folders and files
- View asset metadata, including asset size and content type
- Download asset files
- Publishing Dropbox content from Content Manager
These capabilities make it possible to implement the following use cases (among others):
- Navigate Dropbox assets from one single interface, Tridion Sites
- Consume Dropbox assets in your Component and Pages managed in Tridion Sites
To get started, there are a few quick steps.
Download the zip file in the upper right-hand corner and unpack it. You'll find the JSON configuration file and the connector zip file.
Open up the JSON configuration file and make the following changes. Create an account on DropBox and login using your account.
- Creating an OAuth access token for Dropbox
In the Dropbox Developer's area (https://www.dropbox.com/developers, open the App Console.
- Create a new app.
- Choose the appropriate API.
- Choose the appropriate type of access (folder or full).
- For the app name, you can use whatever you like.
- Open the newly created app
- Under Permission Type click on Scoped App
- Select all the following for permission for the app created
Generate a new Oauth 2 access token and immediately copy it before closing the window. You need this for your configuration of Dropbox in the Connector.
- Open a postman instance and create a new collection.
- On that new collection select the authorization tab where you need to add some info to generate a refresh token:
- type : OAuth 2.0
- Add auth data to : Request url
- Token name: the name you want
- grant type : authorization code
- callback url: keep is as it is and copy that value in your dropbox app from app console at redirect uri and press add
- Auth url: https://www.dropbox.com/oauth2/authorize?token_access_type=offline
- Access token url: https://api.dropboxapi.com/oauth2/token
- client ID : app key from you dropbox app
- Client Secret : app secret from dropbox app
- Scope: empty string
- State: empty string
- Client authentication: send client credentials in body
Go to dropbox and add the redirect URLs for OAuth 2 ( https://oauth.pstmn.io/v1/browser-callback )
Access token url: https://api.dropboxapi.com/oauth2/token
Copy the App Key and click on Show to display the App Secret Key and copy the Secret Key
client ID : app key from you dropbox app
Client Secret : app secret from dropbox app
Client authentication: send client credentials in body
Press Get New Access token button. A web window will open where you need to allow access
After the authorization is successful a window will open with some authentication information, copy the refresh token to configuration file from connector.
So, at this point you should have updated the configuration JSON to include AccessToken, RefreshToken, ClientId, ClientSecret. HostUrl , BearerTokenUrl and DisconnectUrl no need to change its configured as part of the attached zip file.
The final configuration that you need to do is to set up a Stub Folder in Tridion Sites. What exactly is a stub folder? The easiest way to think of it is a virtual folder that points to a set of outside resources. The interesting thing about it is that you can use Tridion's inheritance model to determine if you want to have the connectors available to all publications by putting it high up in the BluePrint hierarchy or by putting lower down for only a few publications. So create your folder and copy the folder's magical TCM ID - it will look something like tcm:2-71-2.
Update the stubFolders field in the JSON file with this information, save and for the configuration part, you are DONE!
So now let's head over to the Tridion Sites Add-On Manager where you will upload the connector. After uploading the zip file, you will need to upload the configuration JSON file that you modified. At this stage you'll notice that the connector is awaiting activation. Simply browse over to Experience Space (or the Content Explorer) and it will activate.