all: use OAuth2 refresh token in storage config #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Dropbox removed support for long-lived access tokens a few years ago:
https://dropbox.tech/developers/migrating-app-permissions-and-access-tokens
This storage implementation thus required re-running the server setup
every 4 hours. By replacing the stored access token with a refresh
token, and using the
oauth2
package implementation of an HTTP clientthat automatically refreshes the access token upon expiry, we can once
again have long-lived access to the Dropbox API. Currently refresh
tokens do not have a default expiry and are not rotated upon access.