[Cyberduck-trac] [Cyberduck] #8880: Authentication using AWS AssumeRole and GetSessionToken with AWS STS

[Cyberduck]

#8880: Authentication using AWS AssumeRole and GetSessionToken with AWS STS
----------------------------+-------------------------
 Reporter:  tigris          |         Owner:  dkocher
     Type:  feature         |        Status:  assigned
 Priority:  low             |     Milestone:
Component:  s3              |       Version:  4.7
 Severity:  normal          |    Resolution:
 Keywords:  s3 iam sts      |  Architecture:  Intel
 Platform:  Mac OS X 10.10  |
----------------------------+-------------------------

Comment (by jibi-waba):

 Both scenarios could/should be supported. Cyberduck should not define best
 practice or method. If the SDK or boto support a specific credentials
 configuration (or cross-account access configuration) for authentication,
 then clients like Cyberduck should also strive to support this
 authentication method(s). We have no issues with other clients, such as
 the AWSCLI or Terraform, supporting aws_session_token, so the expectation
 is that Cyberduck would also support it.

 As you said, this should be a rather simple change since this is standard
 support within the SDK. Perhaps this needs to be split into two separate
 requests, but they’re closely related.

--
Ticket URL: <https://trac.cyberduck.io/ticket/8880#comment:30>
Cyberduck <https://cyberduck.io>
Libre FTP, SFTP, WebDAV, S3 & OpenStack Swift browser for Mac and Windows