When creating new S3 connection, falls back to local profile if error - even if option is off

[DeathMagnet]

Describe the bug
When creating a new AWS S3 connection with access key/credentials for new account, if there is an error with IAM profile, no error is displayed and S3 buckets available to default AWS profile are listed - even with option off.

To Reproduce
Steps to reproduce the behavior:

1. Set up AWS CLI default profile for AWS account A (with full access to S3 buckets)
2. In AWS account B, create IAM user with role/policy that has access to a single S3 bucket in account B - the policy we used did not have an action for s3:ListAllMyBuckets, which should cause an error
3. Create access key/secret key for user in account B.
4. Open CyberDuck and click Open Connection
5. Create new Amazon S3 connection, enter access key/secret key for IAM user to access account B, click Connect
6. Screen flashes and S3 buckets in account A are listed and user has full access (looks like I just logged into account A with account B user)
7. Click Open Connection again
8. Enter access key/secret for IAM user to access account B
9. Error is displayed that user policy is not correct and no s3 buckets are displayed

Expected behavior
Display error that policy is not correct and do not display any S3 buckets

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows 11
• Version: 9.4.1

Log Files

cyberduck.log

Additional context
Add any other context about the problem here.

Checked Preferences->Profile options and the option S3 (Credentials from AWS Command Line Interface) is not selected.

This caused a bunch of red flags to be raised because the person who found this had default CLI access to all S3 buckets in the same account they were adding the user to, so when it failed when they tested in CyberDuck, it appeared to them that the new user had access to all S3 buckets in the account, not just the S3 bucket they were supposed to have access to.

[DeathMagnet]

If you remove the default aws credentials, you get a blank screen (no list of S3 buckets), but no error until you try again.

[hc100]

I have a similar problem with S3 authentication. Steps to reproduce:

• Have a working login to S3 with an IAM user client/secret
• Update the secret with a incorrect string
• Login fails and show pop-up with "The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details. Please contact your web hosting service provider for assistance." (expected behavior)
• Enter the correct secret in the pop-up window and cannot login. (unexpected behavior)
• Close the pop-up window, and update the connection setting with the correct secret.
• Login fails and show pop-up with "The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.(unexpected behavior)
• Repeat

I found that restarting the app fixes the problem after setting the correct secret.

my environment: macos, cyberduck 9.4.1 (44384)

[dkocher]

Please let me know if you can reproduce in version 9.5 or later.