asfenhorizon.blogg.se - Jottacloud test

Jottacloud test code#
Jottacloud test password#
Jottacloud test plus#

Jottacloud test password#

Request new token with token_endpoint url from OpenID configuration, using a hard coded client_id, and with password authentication using credentials from the LoginToken.

Jottacloud test code#

Request OpenID configuration using well_known_link url from parsed LoginToken (only need the token_endpoint property, so could possibly hard code it and skip this step?).

Parse the entered login token string into a LoginToken object.

Clicking OK, Save or whatever (I've never used the service), the user is presented with an authid which he must copy to Duplicati and save in the backend configuration.

User must copy the login token string from Jottacloud and paste into the Duplicati OAuth handler input field.

User must navigate to, log in to his Jottacloud account, and click the button to generate a new "Personal Login Token".

May for convenience also show a clickable link to.

Clicking the Jottacloud button just shows an input box for user to manually enter a "Personal Login Token".

Meanwhile, Jottacloud Error 401 (Unauthorized) has a workaround (with drawbacks) of Rclone storage type to get to Jottacloud.įrom what I understand then, the Duplicati OAuth handler service must be updated: I would suggest looking into Jottacloud as best we can, to see if OAuth without Open ID Connect will do, considering who does what in Duplicati, and maybe reading the Python code of the OAuth handler to try to see if it looks plausible, then ask its admin. In terms of priority, I suppose between this and the forum topic, we might see all the users who are still interested in Jottacloud.ĭevelopers are scarce (any volunteers?), but if this can be done by and a small OAuth handler change, it "might" fit. In terms of release, it is not clear if new Beta can be pushed out just for this, but in any case we would want it in a Canary at first. I'm not sure who did the original Jottacloud ones. Somebody would have to change some GUI screens. The latter person has been rarely available, but did help Dropbox, so might help here. So there's hope, but the Jottacloud new-way needs to be checked further, and several people may be needed, one for Duplicati and one for the Duplicati OAuth handler.

Duplicati can handle either, so Updated values to match current Dropbox API changed the OAuth handler end, and 2.0.6.101_canary_ did a required client-side change. 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. 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.

Jottacloud test plus#

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.

Create a backup with Jottacloud as the backend.

This was confirmed by Jottacloud staff in a tweet: Steps to reproduce It is no longer possible to connect to Jottacloud with Duplicati, it always returns a 401 error. This was discontinued without warning yesterday.

Jottacloud used to support basic authentication using user_id and password.

I have searched the forum for related topics.

I have searched open and closed issues for duplicates.