expired_access_token error from Dropbox short-lived access tokens #4667 describes how Dropbox recently took the refresh token path (breaking Duplicati) instead of a long-lived access token. If this can be pulled off, Jottacloud backend would have AuthID which it gives to the OAuth handler which handles token refresh.
#Jottacloud cannot connect code#
There's a fairly standard way in the C# code (I think) to interface with the Duplicati OAuth handler to serve as a Jottacloud model. shows how the current Duplicati OAuth services were set up. I suspect client type is a small factor in its flow. How we get along with OAuth and oauth-handler code shows Duplicati takes a different approach, using a cloud-resident OAuth confidential client, but (just like rclone), it might be able to do the needed OAuth. At a code level, the fact that they pass jottacli as the client ID, and don't bother passing the client secret (because secrets are hard to keep with an installed program) is OAuth-flavored too. Someone who's tried it can say if user's web flow goes like An Illustrated Guide to OAuth and OpenID Connect. I don't really do Go language or C#, or Python, but the linked code from rclone looks like Jottacloud "legacy" plan is going away, whereas their "standard" plan is their new way. On the plus side, with the token it is possible to enable 2FA on your Jottacloud account, which was previously incompatible with Duplicati. It appears that the only way to continue supporting Jottacloud is to use the token. Note: rclone supports using Jottacloud's "personal login token", which is used by their command line app.
0 kommentar(er)
