Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Service Accounts : Path Error #12

Closed
iminamoto opened this issue Jul 16, 2022 · 1 comment
Closed

Service Accounts : Path Error #12

iminamoto opened this issue Jul 16, 2022 · 1 comment
Labels
question Further information is requested Resolved Error/Bug successfully fixed!

Comments

@iminamoto
Copy link

No description provided.

@TheCaduceus
Copy link
Owner

TheCaduceus commented Jul 16, 2022

@iminamoto By seeing your given Traceback, it is clear that you are trying to use your Service Accounts. For your information! while using Service Accounts to make your rclone remotes, you need to provide the path of one .json file otherwise providing any other path or invalid path trigger this Error because Rclone was not able to show Shared Drive list due to lack of credentials which it collects from .json files. I do like to recommend you to read Rclone Docs before opening any issue here.

TraceBack:

Fatal error: failed to make Fs to list Shared Drives: drive: failed when making oauth client: failed to create oauth client from service account: error processing credentials: google: read JWT from JSON credentials: 'type' field is "" (expected "service_account")

@TheCaduceus TheCaduceus added question Further information is requested Resolved Error/Bug successfully fixed! labels Jul 16, 2022
@TheCaduceus TheCaduceus changed the title Fatal error: failed to make Fs to list Shared Drives: drive: failed when making oauth client: failed to create oauth client from service account: error processing credentials: google: read JWT from JSON credentials: 'type' field is "" (expected "service_account") Service Accounts : Path Error Jul 16, 2022
@TheCaduceus TheCaduceus pinned this issue Jul 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested Resolved Error/Bug successfully fixed!
Projects
None yet
Development

No branches or pull requests

2 participants