[Cyberduck-trac] [Cyberduck] #10546: S3 STS looking in .aws/credentials instead of .aws/config
Cyberduck
trac at cyberduck.io
Thu Nov 29 02:15:42 UTC 2018
#10546: S3 STS looking in .aws/credentials instead of .aws/config
-------------------------+-------------------
Reporter: gbws2018 | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: core | Version: 6.8.3
Severity: normal | Keywords:
Architecture: | Platform:
-------------------------+-------------------
Hi,
I have noticed quite an annoying issue with the current implementation of
S3 + STS + mfa token.
It is working but only if all the config is inside .aws/credentials and
ignores totally .aws/config.
This goes against how the AWS cli is implemented.
AFAIK .aws/credentials is only supposed to contain the keypair and
.aws/config is where the source_profile, mfa_serial, role_arn is stored.
Cyberduck is only working if all the information is stored inside
.aws/credentials.
Gregory
--
Ticket URL: <https://trac.cyberduck.io/ticket/10546>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows
More information about the Cyberduck-trac
mailing list