Not sure if dropbox refresh-token support is there?
Planning to use rclone in an headless embedded device where there won't be any user interaction possible.
Dropbox mentions I should use the long-lived "refresh token's which can be used to obtain new access tokens : _https://oauth.net/2/grant-types/refresh-token/
but haven't been able to generate a config file with them, and haven't seen any code in the repo to support this.
Dropbox is planning to drop the tokens with "no expiration" in "mid 2021".
If this is not possible, any suggestions on a service which is better suited for 'no later' user interaction would be greatly welcomed.
Thank you..
Oz
What is your rclone version (output from rclone version)
I received an email from dropbox about this a couple of days ago. I checked my config file - all of my tokens have no expiry.
I tried refreshing the toke (with rclone config reconnect dropbox:) but I still didn't get a token with an expiry.
I'm not quite sure what needs to be done to rclone - rclone supports refresh tokens and token expiry already (they in use by most of the other oauth backends), so it should just be a matter of enabling it somehow!
If you have any ideas as to what needs to be done, I'd be grateful for any input
A brief skip of the blog indicates that what rclone needs to do is ask for some scopes on the initial Oauth.
It looks like dropbox will then return a refresh token and a token with an expiry.
Dropbox also supports PKCE which would be a good thing for rclone to support.
Thank you for looking into this.. I did end up with Azure blob storage, again with rclone of course..
I think you can test the short term key usecases by creating a new development app, the default option is short term keys, and warns about deprecated long term keys.
I don't have posted here directly because the forum seems to block me when i try to post the answer (due to some URL things in the text, i don't know why)
