Cyberduck Mountain Duck CLI

Changes between Initial Version and Version 1 of Ticket #8610, comment 8


Ignore:
Timestamp:
Feb 25, 2015 11:33:07 AM (4 years ago)
Author:
ebekker
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #8610, comment 8

    initial v1  
    33Instead of touching any of the UI elements at all, a special sentinel value, such as {{{%IAM_ROLE%}}}, that when provided for the "Access Token" of an S3 connection (i.e. the Username), triggers slightly different behavior in the S3 connection building.
    44
    5 Looking at the latest version of the code base in trunk for S3Session.java (source/ch/cyberduck/core/s3/S3Session.java @ r17003), at line 114 where you handle switching between an anonymous connection (null AWSCredentials) or constucting a set of credentials based on user-provided Access Key + Secret Key, you could add a third option when {{{"%IAM_HOST%".equals(host.GetCredentials().GetUsername())}}} to construct an {{{AWSSessionCredentials}}} instance.
     5Looking at the latest version of the code base in trunk for S3Session.java (source/ch/cyberduck/core/s3/S3Session.java @ r17003), at line 114 where you handle switching between an anonymous connection (null AWSCredentials) or constucting a set of credentials based on user-provided Access Key + Secret Key, you could add a third option when {{{IAM_ROLE_SENTINEL.equals(host.GetCredentials().GetUsername())}}} to construct an {{{AWSSessionCredentials}}} instance.
    66
    77The Access Key, Secret Key and Session Token would all be derived from the running context as described above.
swiss made software