the email is mine, the dropbox admin.
I tried without the /
rclone --dropbox-impersonate rxxxxxxx@xxxxxxx.com lsd dpbx:
2021/04/09 17:15:12 Failed to create file system for "dpbx:": invalid dropbox team member: "rxxxxxxx@xxxxxxx.com": missing_scope/..
When I read the man it would seem I have to use the --dropbox-impersonate for the rclone config?
--dropbox-impersonate
Impersonate this user when using a business account.
Note that if you want to use impersonate, you should make sure this flag is set when running "rclone config" as this will cause rclone to request the "members.read" scope which it won't normally. This is needed to lookup a members email address into the internal ID that dropbox uses in the API.
Using the "members.read" scope will require a Dropbox Team Admin to approve during the OAuth flow.
You will have to use your own App (setting your own client_id and client_secret) to use this option as currently rclone's default set of permissions doesn't include "members.read". This can be added once v1.55 or later is in use everywhere.
Well so far not much luck even with the forked version:
$ rclone version
rclone v1.55.0-beta.5175.aee3bfb17.fix-dropbox-scopes
os/arch: linux/arm
go version: go1.16rc1
I access my personal folder but not the Teams shared folder....
still the same error all the time:
$ rclone lsd dpbx:/
2021/04/09 22:16:30 Failed to create file system for "dpbx:/": get current account failed: missing_scope/.
and
$ rclone --dropbox-impersonate rxxxxxxxxxxxx lsd dpbx:/
2021/04/09 22:17:16 Failed to create file system for "dpbx:/": invalid dropbox team member: "xxxxxxxxxxxxx": missing_scope/.
Saddly, rclone is no longer working with Dropbox business. So bad...
And the issue is clearly coming from Dropbox themselves.
Shame on them...
Finally I have use Multcloud and setup an FTP on my NAS-Rpi . Multcloud does work very well with DropBox business Teams folders. So I use Multcloud for accessing Dropbox business and then backup all my Team folders to my NAS-Rpi via SFTP (SHH ftp actually). I did not want to do that as I have now to watch and protect some ports on my Rpi-NAS and on my router... but this is life...
For what its worth, I managed to set a new team app up today, there seems to be a bug (at least with some rclone versions) not requesting the proper scope, but I managed to manually add the scope to the URL when authorizing the App with your Dropbox business team.
And then it works fine for me.
I ran the config with the --dropbox-impersonate flag (and a team admin email ) and in the generated URL that gave the error about missing scope I manually in the URL inserted "manually add "+team_data.member" and then I could authorize the app and get it to work.
EDIT: also confirmed this bug (and successful workaround) on below build:
rclone v1.55.0
Yes, this build correctly requests the team_data.member scope in the generated URL, which makes the error go away.
With this I could successfully setup a new Dropbox remote with rclone towards a team-centric Dropbox app.