Jottacloud, whitelabels and login

Help and Support
1

What is the problem you are having with rclone?

When I tries to logon to Jottacloud (one whitelabel version from ComHem) I only get an error message. I'v read a few threads about it and it seems like I have to use an Beta version. I trying with the beta version v1.52.1-053-gdc24ccc9-jotta-legacy-auth-beta but still only get an error. Is there anyone that have an idea?

What is your rclone version (output from rclone version)

v1.52.1-053-gdc24ccc9-jotta-legacy-auth-beta

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Linux Debian 64bit

Which cloud storage system are you using? (eg Google Drive)

Jottacloud (Whatelabel Comhem)

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone config

The rclone config contents with secrets removed.

Paste config here

A log from the command with the -vv flag

Failed to get oauth token: HTTP error 400 (400 Bad Request) returned body: "{\"error\":\"invalid_grant\",\"error_description\":\"The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.\"}"
2

hello and welcome to the forum,

that is an old beta of an old version of rclone.

best to test with the latest stable is v1.53.2

1 Like
3

The fix you are referring to are out of beta and was released in version 1.53:

Jottacloud

  • Bring back legacy authentification for use with whitelabel versions (buengese)

See also the documentation on legacy setup of Jottacloud backend.

1 Like
4

Thanks for the quick reply :slight_smile:

I just tried the latest stable one (v1.53.2) and I still get an error message. I'm not really shure why I get it.

2020/11/06 09:14:43 Failed to get oauth token: HTTP error 400 (400 Bad Request) returned body: "{"error":"invalid_grant","error_description":"The provided authorization grant (e.g., authorization code, resource owner credentials) or refresh token is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client."}"

5

Could it be that your whitelabel provider has moved from the legacy authentication method and now uses what the "parent" jottacloud service currently uses? Does your provider have the web page to generate token in your account security settings in web interface (for example at https://cloud.comhem.se/web/secure)? If so, you should try creating a new (temporary) rclone remote using the "default" setup method.

6

unfortnaly my provider don't allow me to generate any token. I can logon to the service with the same credential on their webpage.

7

OK. If you haven't already, try re-create a (temporary) remote, even with the legacy method, just in case. I do not have the full view of the authentication parts in play here, so I am unfortunately not sure what to try next. Hopefully someone that do will chip in.. Perhaps it qualifies for an issue already.

8

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.