We all know it's preferable to authorize rclone with a service account. Service-accounts practice POLP by reducing the permissions scope to only the narrow permissions needed to complete the task. Using user permissions give rclone broad access to your account.
This guide explains how to obtain a service account access-token via gcloud CLI without generating a service-account-keys. Service-account keys are an issue because (a) they can be breached and (b) they are a pain to generate. An account-token is temporary
A few more benefits of using service accounts with access tokens (instead of json key files)
The tokens are temporary and expire when you want them to
no need for the clumsy oauth flow. this is great on remote SSH without access to a web browser
You don't need to authorize the Rclone App ID to your account. The Rclone APP ID authoriztation opens up access to your google account to the rclone app ID owner.
Why are you getting the access token for the dev-gcloud-go service account when you created the gcs-read-only service account for rclone to use to access to GCS bucket? Isn't it just ending up using the permissions applied to the dev-gcloud-go account?
Hi @Tony_M, I try to use short live token but I have the error failed to configure Google Cloud Storage: google: could not find default credentials.. It's seem like the client still try using ADC instead token, do you have an idea ?