-
Notifications
You must be signed in to change notification settings - Fork 156
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
Impossible to use signed url v4 and the Service Account Credential APIs #355
Comments
I'm facing the same issue on cloud function env, and getting the error below:
|
@guillaumeblaquiere at the line Any idea? |
@deepamgupta can you describe your runtime context? Is it on your workstation? On Compute Engine? elsewhere? |
@guillaumeblaquiere Currently I am working on my Laptop. Using Pycharm debugger to run a flask application. |
I ran into the same problem trying to run a simple FastAPI app on Cloud Run just today. Just an FYI that the problem still exists. Also, thank you for your article. It allowed me to build the work around. |
Same issue here with v4 and FastAPI. |
Months ago, I solved an issue to a Stack overflow user by explaining how to generate a signed URL without a service account JSON fey file. I also release an article on this
Today, a comment of a user told me that is doesn't work. They open a new Stack Overflow question and in their question, there is the v4 mentioned.
I dug into the code and yes, the v2 and the v4 haven't the same behavior: the v4 check if the credential can generate a signed URL by itself, that implies the useless check later that allows to use Service Account Credential API, instead of the service account private key to generate the signature.
Environment details
python --version
3.7 and 3.8google-cloud-storage
version: latest (1.35.0)Steps to reproduce
Only the version (v2/v4) has changed
Fix proposal is coming.
The text was updated successfully, but these errors were encountered: