-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Unable to read objects in GCS after a first request with GS_NO_SIGN_REQUEST #11964
Comments
Update: thanks to this related issue I learnt about |
rouault
added a commit
to rouault/gdal
that referenced
this issue
Mar 18, 2025
Loading
Loading status checks…
…hen changing authentication parameters Fixes OSGeo#11964
rouault
added a commit
to rouault/gdal
that referenced
this issue
Mar 18, 2025
Loading
Loading status checks…
…hen changing authentication parameters Fixes OSGeo#11964
rouault
added a commit
that referenced
this issue
Mar 19, 2025
Loading
Loading status checks…
…hen changing authentication parameters Fixes #11964
Jwohnlf
pushed a commit
to Jwohnlf/gdal
that referenced
this issue
Mar 23, 2025
…hen changing authentication parameters Fixes OSGeo#11964
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the bug?
Trying to read files from Google Cloud Storage with auth config options (like
GS_OAUTH2_PRIVATE_KEY
andGS_OAUTH2_CLIENT_EMAIL
) always fails if a previous unauthenticated request (withGS_NO_SIGN_REQUEST=YES
) was made.For context, I want to first check if they can be publicly accessed and, if not, follow up with a signed request. While the signed requests on their own work fine, they always fail in the above stated case. No amount of other config options (like using
GS_NO_SIGN_REQUEST=NO
or trying to disable the VSI cache) fix the issue.Steps to reproduce the issue
gs://stac-private-bucket/clouds.tif
Authenticated read works as expected
Authenticated read after an unauthenticated read fails
Versions and provenance
GDAL version: GDAL 3.10.2, released 2025/02/11
Operating system: macOS Sonoma 14.5 (23F79)
Installed via homebrew
Additional context
No response
The text was updated successfully, but these errors were encountered: