2.2 KiB
Google Cloud Troubleshooting Guide
Error: "401 Anonymous caller" or "403 Permission 'storage.objects.list' denied"
If you successfully authenticated with the Authenticate Google Cloud operation but received a 401 or 403 error when trying to run an operation like GCloud List Bucket or GCloud Read File, the issue is Identity and Access Management (IAM).
Even though your token is valid (Authentication), your Google Account does not have the necessary permissions (Authorization) to perform that specific action on that specific resource.
How to Fix IAM Permissions
-
Verify Your Google Login Account Make sure the email address you selected in the Google Login popup is the exact same email address that holds permissions in your Google Cloud Project.
-
Grant Storage Roles To read from Cloud Storage, your Google Account must be granted a role that contains the required permissions (like
storage.objects.listandstorage.objects.get).- Go to the Google Cloud Console.
- Navigate to IAM & Admin > IAM.
- Find your email address in the list of principals.
- Click the pencil icon (Edit principal) next to your name.
- Click Add Another Role.
- To fully utilize the CyberChef Cloud Storage operations, add the Storage Object Viewer role (or Storage Object Admin if you plan to write files later).
- Click Save.
Note: IAM changes can take anywhere from 60 seconds to a few minutes to propagate across Google's infrastructure.
-
Check Bucket-Level Permissions If the bucket belongs to a different project than your OAuth Client ID, or has "fine-grained" access control instead of "Uniform" access control, you may need to grant yourself permission directly on the bucket itself.
- Navigate to Cloud Storage > Buckets.
- Click on the bucket you are trying to read.
- Go to the Permissions tab.
- Click Grant Access.
- Add your Google email address and assign the Storage Object Viewer role.
-
Retry the Operation After waiting two minutes for IAM propagation, refresh CyberChef (this forces a new session and drops the old token). Re-authenticate with Authenticate Google Cloud, then bake the recipe again.