Difference between revisions of "ServiceException: 401 Anonymous caller"
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
* <code>[[GOOGLE_APPLICATION_CREDENTIALS]]</code> | * <code>[[GOOGLE_APPLICATION_CREDENTIALS]]</code> | ||
* <code>[[gcloud iam service-accounts keys create]]</code> | * <code>[[gcloud iam service-accounts keys create]]</code> | ||
| − | * <code>[[gcloud auth activate-service-account]]</code> | + | * <code>[[gcloud auth activate-service-account]] --key-file=[[your_key_file_name.json]]</code> |
* <code>[[gcloud projects list]]</code> | * <code>[[gcloud projects list]]</code> | ||
== See also == | == See also == | ||
| − | * {{ | + | * {{GCP}} |
[[Category:GCP]] | [[Category:GCP]] | ||
Latest revision as of 07:17, 22 June 2022
ServiceException: 401 Anonymous caller does not have storage.objects.list access to the Google Cloud Storage bucket.
Related[edit]
GOOGLE_APPLICATION_CREDENTIALSgcloud iam service-accounts keys creategcloud auth activate-service-account --key-file=your_key_file_name.jsongcloud projects list
See also[edit]
- Google Cloud Platform, Google Cloud organizations, Google Cloud projects, Google Cloud SDK,
gcloud, gsutil, bq, Cloud Build, Google Cloud Operations, Google Cloud free tier, Google App Engine, Cloud Run, BigQuery, Google Secret Manager, Google Cloud Spanner, Looker, Google Cloud Deployment Manager, Google Cloud Shell, console.cloud.google.com/, Google Site Verification API, Anthos, Google Cloud IAM, Vertex AI, Google Cloud Dataflow, Google APIs, Google Cloud Registry, Google cloud role, Cloud Scheduler, Google OS Config Agent, Google Cloud Logs Explorer, Google Cloud error reporting, Google Cloud Platform timeline, GCP KMS, GCP log explorer, GCP machine families, regions, Cost sentry, Cloud Trace, AlloyDB, Cloud TPU, Google Sign-In for server-side apps, Google Cloud Setup
Advertising:
