When creating the config for Zoho WorkDrive, after I authorize through the browser and select a team, I get the message "Error: no items found in: Workspace ID". Any attempts to access the remote afterwards yields a 401 Unauthorized error. The browser authorization shows a success message, and config is able to correctly list the team drives I have access to. I've tried this on both my local machine and a virtual machine, with the same results. I get the same error regardless of the team drive I select. I have WorkDrive through a Zoho Workplace Professional license. If it's relevant, I am also part of an organization where I have admin access, but I am not the super admin.
Run the command 'rclone version' and share the full output of the command.
Which cloud storage system are you using? (eg Google Drive)
Zoho WorkDrive
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone config
rclone lsd remote:
The rclone config contents with secrets removed.
[[redacted]]
type = zoho
region = com
token = {"access_token":[[redacted]],"token_type":"Zoho-oauthtoken","refresh_token":[[redacted]],"expiry":"2022-05-16T11:49:55.6330496-04:00"}
What that means is that rclone tried to look up your workspace IDs and didn't find any, so couldn't complete the configuration.
If you know the ID then you can put it in your config
root_folder_id = XXXX
And things should start working.
Can you run rclone config -vv --dump bodies and run through the config again.
Can you post the last HTTP transaction so the request for /teams/XXX/workspaces and the corresponding response and hopefully we can get to the bottom of this.
Feel free to redact any information you think might be confidential.
So, here's everything from the point where I set the team drive ID to where it gives the error. It's a 200 OK response, but the expiration date seems off.
It turns out the issue is that I was expecting the WorkDrive implementation to work differently than it actually does.
I didn't have any Team Folders set up, because we're still working how to set those up within our organization. So, I set up a team folder "Test", the id for that was detected successfully, and everything works as it should. I'm guessing that means different team folders have to be set up as different remote drives, then. It also doesn't seem possible to access or do anything with my personal drive files, although that's unnecessary for the specific application I'm looking to use rclone for.
No, it doesn't seem to show up as a workspace, which is why I was having issues with rclone not being able to find workspaces. I found this API documentation, and it seems like getting "My Folders" is a different process where you need a team member id, and then it's [team member id]/privatespace