[Storage] Easily generate signed URLs when using workload identity
I maintainer di solito rispondono entro 1 giorno
@rajeevpodar ci sta già lavorando.
Dal 9/10/2026.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Stack tecnologico
- google-cloud, ruby
- Ambito
- api, authentication, cloud
Direzione di ricerca
Inizia da File#signed_url e dal percorso signer_v2.rb indicato nell’errore, quindi traccia il modo in cui vengono gestiti gli argomenti issuer e signer. Confronta il flusso esistente basato sulle chiavi con gli esempi di workload identity e IAM signBlob nell’issue. Il lavoro è completato quando workload identity può generare URL firmati tramite un’API supportata e documentata, senza richiedere ai chiamanti di costruire autonomamente il signer.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Hi, I am open to writing a PR to make code changes for this feature but wanted to start with an issue to get feedback.
When developing locally I can generate signed URL simply with:
require "google/cloud/storage"
storage = Google::Cloud::Storage.new(
project_id: "<project_id>",
credentials: ENV["GCP_CREDENTIALS_PATH"]
)
bucket = storage.bucket "<bucket_name>"
remote_file = bucket.file "foo/bar", skip_lookup: true
url = remote_file.signed_url method: "PUT", content_type: "application/json"
However, when running my code from within an eks pod with access grant via workload identitiy (https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity)
I get the error:
/usr/local/bundle/gems/google-cloud-storage-1.31.1/lib/google/cloud/storage/file/signer_v2.rb:88:in `determine_issuer': Service account credentials 'issuer (client_email)' is missing. To generate service account credentials see https://cloud.google.com/iam/docs/service-accounts (Google::Cloud::Storage::SignedUrlUnavailable)
Based on https://github.com/salrashid123/gcpsamples/blob/master/gcs_keyless_signedurl/main.py I was able to write some equivalent ruby code that works for generating a working signed URL (not the most well-factored code, just a proof-of-concept)
require "google/cloud/storage"
storage = Google::Cloud::Storage.new
bucket = storage.bucket "<bucket_name>"
remote_file = bucket.file "foo/bar", skip_lookup: true
path = "/#{bucket.name}/#{remote_file.name}"
url_manually = "https://storage.googleapis.com#{path}"
access_token = JSON.parse(`curl -s -H 'Metadata-Flavor: Google' http://metadata/computeMetadata/v1/instance/service-accounts/default/token`)["access_token"]
connection = Faraday.new(url: "https://iamcredentials.googleapis.com/v1/projects/-/serviceAccounts/#{service_account_email}:signBlob") do |conn|
conn.request :json
end
expiration = 1.day.from_now.to_i
verb = "PUT"
content_md5 = ""
content_type = "application/json"
signature_string = "#{verb}\n#{content_md5}\n#{content_type}\n#{expiration}\n#{path}"
response = connection.post do |req|
req.headers["Authorization"] = "Bearer #{access_token}"
req.body = {delegates: [], payload: Base64.encode64(signature_string).gsub("\n","")}
end
signed_blob = JSON.parse(response.body)["signedBlob"]
signed_url = url_manually + "?" + URI.encode_www_form("GoogleAccessId": service_account_email, "Expires": expiration, "Signature": signed_blob)
So... I was thinking perhaps we could/should just change the implementation of signed_url to detect the conditions under which key-based signing will fail and automatically attempt this meta data service token + signBlob service method.
Or perhaps it's already exposed somewhere else within the depths of this ruby gem? (in which case in the very least the error message you see could be updated to point that out)
Thanks,
Jacob
Update based on https://googleapis.dev/ruby/google-cloud-storage/latest/Google/Cloud/Storage/File.html#signed_url-instance_method I have a better version
require "google/cloud/storage"
storage = Google::Cloud::Storage.new
bucket = storage.bucket "<bucket_name>"
remote_file = bucket.file "foo/bar", skip_lookup: true
issuer = "<service account email>"
signer = lambda do |string_to_sign|
IAMCredentials = Google::Apis::IamcredentialsV1
iam_client = IAMCredentials::IAMCredentialsService.new
scopes = ["https://www.googleapis.com/auth/iam"]
iam_client.authorization = Google::Auth.get_application_default scopes
request = Google::Apis::IamcredentialsV1::SignBlobRequest.new(
payload: string_to_sign
)
resource = "projects/-/serviceAccounts/#{issuer}"
response = iam_client.sign_service_account_blob resource, request
response.signed_blob
end
signed_url = remote_file.signed_url method: "PUT", content_type: "application/json", issuer: issuer, signer: signer
And the only things that are "custom" to my use case in this example end up being arguments into the signed_url method. so perhaps a simplification this gem could make would be to auto-generate the signer proc
Finally, I need a way to tell which version of the signed_url method args to use.
When running locally I have a credentials JSON file. so I need only call remote_file.signed_url method: "PUT", content_type: "application/json"
Whereas from my pod I have to call remote_file.signed_url method: "PUT", content_type: "application/json", issuer: issuer, signer: signer
If I do it backwards (specify an issue and signer when not on a pod) I get
/Users/jacob/.gem/ruby/3.0.1/gems/googleauth-0.16.2/lib/googleauth/application_default.rb:76:in `get_application_default': Could not load the default credentials. Browse to (RuntimeError)
https://developers.google.com/accounts/docs/application-default-credentials
for more information
Is there some simple call I could make to this gem to determine what context I'm in?
- Lingua principale
- Ruby
- Stelle
- 1.4k
- Fork
- 581
- Merge medio
- 1g 22h
- PR unite (30g)
- 69
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di googleapis/google-cloud-ruby
-
eMudhra/emSign CA compromise (October 2026): what Cloud SDK Ruby Libraries developers need to doForse già presa @viacheslav-rostovtsev l’ha presa 13 giorni fa. Apertatype: process
googleapis/google-cloud-ruby#36690 · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
chore(ci): remove temporary Windows grpc < 1.85.0 pin once x64-mingw-ucrt gem is publishedForse già presa @viacheslav-rostovtsev l’ha presa 21 giorni fa. Apertagrpc priority: p1 type: cleanup
googleapis/google-cloud-ruby#36677 · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
[google-cloud-datastore] timeout option has no effect: per-RPC defaults override it (same as #14050)Apertaapi: datastore priority: p2 type: bug
googleapis/google-cloud-ruby#36632 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
storage/bigquery: google-apis-* dependency floors are lower than the wrappers actually requireForse di nuovo libera @kalragauri l’ha presa 34 giorni fa e non c’è nessuna pull request aperta. Apertaapi: storage priority: p3 type: bug
googleapis/google-cloud-ruby#36610 · 2 commenti · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
Support `STORAGE_EMULATOR_HOST` in the `google-cloud-storage` GemForse già presa @rajeevpodar l’ha presa 38 giorni fa. Apertaapi: storage priority: p2 type: feature request
googleapis/google-cloud-ruby#34022 · 1 commento · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di googleapis/google-cloud-ruby
Issue simili
-
Difficoltà 1/5 1-3 ore Idoneità per principianti 66/100
philippe-nougaillon/coopcomm#543 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
we-promise/sure#5191 ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
-
Supoort VXBilibili linksApertaSource Support
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
palkan/action_policy#316 ·