Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Failure configuring credentials from AWS CLI setup #14970

Closed
Xarno opened this issue Aug 7, 2023 · 9 comments · Fixed by #14973
Closed

Failure configuring credentials from AWS CLI setup #14970

Xarno opened this issue Aug 7, 2023 · 9 comments · Fixed by #14973
Assignees
@dkocher
Labels
bug s3 AWS S3 Protocol Implementation
Milestone
8.6.3

Comments

@Xarno
Copy link

Xarno commented Aug 7, 2023

Describe the bug
The version 8.6.2 fails to connect to S3 when using SSO credentials. The error message is „Cannot read bucket location.“
Version 8.6.0 is not affected and works correctly.
From the logfiles it looks like the x-amz-security-token header is not send.

To Reproduce
Steps to reproduce the behavior:
Setup an AWS SSO connection (new or old format does not matter)
Try to connect

Expected behavior
Working sso ;)

Desktop (please complete the following information):

  • OS: MacOs 13.5

Log Files
cyberduck_8.6.0.log
cyberduck_8.6.2.log
@dkocher dkocher added the s3 AWS S3 Protocol Implementation label Aug 7, 2023
@dkocher
Copy link
Contributor

dkocher commented Aug 7, 2023

Relates to #13377.

@dkocher dkocher self-assigned this Aug 7, 2023
@jasonbrd
Copy link

jasonbrd commented Aug 7, 2023

+1 Issue does not happen on rollback to 8.6.0.

@jbarnhill-vk
Copy link

+1 8.6.2 also doesn't seem to like profile/assume role in .aws/credentials file

@dkocher dkocher added the bug label Aug 7, 2023
@dkocher dkocher changed the title Version 8.6.2 - S3 get Bucket location fails on connections with SSO setup Failure configuring credentials from AWS CLI setup Aug 7, 2023
@dkocher
Copy link
Contributor

dkocher commented Aug 7, 2023

Regression from #14799 and affects connections using the S3 (Credentials from AWS Command Line Interface) connection profile 1.

Footnotes

  1. https://github.com/iterate-ch/profiles/blob/main/S3%20(Credentials%20from%20AWS%20Command%20Line%20Interface).cyberduckprofile ↩

dkocher added a commit that referenced this issue Aug 7, 2023
@dkocher
Fix #14970.
fbec855
@dkocher dkocher added this to the 8.7.0 milestone Aug 8, 2023
dkocher added a commit that referenced this issue Aug 8, 2023
@dkocher
Fix #14970.
99a2dca
@dkocher dkocher linked a pull request Aug 8, 2023 that will close this issue
Fix #14970. #14973
Merged
dkocher added a commit that referenced this issue Aug 8, 2023
@dkocher
Merge pull request #14973 from iterate-ch/bugfix/GH-14970-hotfix
4fe4d32 
Fix #14970.
@dkocher dkocher modified the milestones: 8.7.0, 8.6.3 Aug 8, 2023
@dkocher dkocher closed this as completed Aug 8, 2023
This was referenced Aug 8, 2023
Closed
Open
@dkocher
Copy link
Contributor

dkocher commented Aug 10, 2023

Version 8.6.3 with a fix has now been released.

@jasonbrd
Copy link

Issues resolved in Cyberduck, but still present in MountainDuck. Where can that issue be tracked?

@dkocher
Copy link
Contributor

dkocher commented Aug 11, 2023

Issues resolved in Cyberduck, but still present in MountainDuck. Where can that issue be tracked?

Please upgrade to Mountain Duck 4.14.3

@srober22utm
Copy link

The MacOS links on both the main Mountain Duck page and the changelog page say "Not found: the resource cannot be found."

@dkocher
Copy link
Contributor

dkocher commented Aug 11, 2023

The MacOS links on both the main Mountain Duck page and the changelog page say "Not found: the resource cannot be found."

The links have been fixed, thanks for notifying us about the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dkocher dkocher

Labels
bug s3 AWS S3 Protocol Implementation
Projects
None yet
Milestone
8.6.3
Development

Successfully merging a pull request may close this issue.

Fix #14970. iterate-ch/cyberduck
5 participants
@dkocher @Xarno @jbarnhill-vk @jasonbrd @srober22utm