rclone/backend/s3
Nick Craig-Wood 2dcb327bc0 s3: fix rclone ignoring static credentials when env_auth=true
The SDKv2 conversion introduced a regression to do with setting
credentials with env_auth=true. The rclone documentation explicitly
states that env_auth only applies if secret_access_key and
access_key_id are blank and users had been relying on that.

However after the SDKv2 conversion we were ignoring static credentials
if env_auth=true.

This fixes the problem by ignoring env_auth=true if secret_access_key
and access_key_id are both provided. This brings rclone back into line
with the documentation and users expectations.

Fixes #8067
2024-09-17 16:07:56 +01:00
..
gen_setfrom.go s3: update to using AWS SDK v2 - fixes #4989 2024-08-07 12:13:13 +01:00
s3_internal_test.go s3: fix Cloudflare R2 integration tests after SDKv2 update #4989 2024-08-07 12:13:13 +01:00
s3_test.go s3: update to using AWS SDK v2 - fixes #4989 2024-08-07 12:13:13 +01:00
s3.go s3: fix rclone ignoring static credentials when env_auth=true 2024-09-17 16:07:56 +01:00
setfrom.go s3: update to using AWS SDK v2 - fixes #4989 2024-08-07 12:13:13 +01:00
v2sign.go s3: update to using AWS SDK v2 - fixes #4989 2024-08-07 12:13:13 +01:00