DropBox New Access Token Policy
DropBox began retiring long-lived (no expiry) access tokens starting Sept 30, 2021 in favor of short-lived tokens and refresh tokens.
With this change, we have opened GIT case JB4-#1847 to address this issue and released a patch and updated instructions to support DropBox authentication via refresh tokens. Please follow the instructions below to apply this patch on your JetBackup 4 Installation:
- Execute the following command on your server terminal to install the DropBox patch:
cd / && curl -L http://repo.jetlicense.com/patches/jetbackup4/issue-JB1847.tar.gz > jb4-issue1847patch.tag.gz && tar -xzf jb4-issue1847patch.tag.gz
- Update the JetBackup cron to add the jetapps-dropbox cron binary
echo "0 * * * * root /usr/local/jetapps/usr/bin/dropbox-cron > /dev/null 2>&1" >> /etc/cron.d/jetbackup
Continue with the steps below if you already have a DropBox Destination Configured in JetBackup
- Visit and sign into your DropBox App Console > Select your DropBox Application that corresponds to your DropBox Destination.
- Under the Settings Tab, scroll down to the OAuth 2 Section, specify
https://auth.jetbackup.com/dropbox/under Redirect URIs then click Add.
- Go back to JetBackup and edit your DropBox destination > Click on "Request Access Code" and the JetBackup-DropBox Authentication Code window will appear.
NOTE: If you are not redirected to auth.jetbackup.com for the access code OR receive a "redirect URI mismatch" error, try refreshing the page with Cntrl+F5 to clear the browser cache.
- Copy the code generated and paste it under the "Access Code" text area then hit "Save".
JetBackup will now be able to refresh tokens automatically and allow you to continue using DropBox.
Our apologies for the inconvenience caused and thank you for your understanding regarding this matter.