Cyberduck Mountain Duck CLI

Changes between Initial Version and Version 1 of Ticket #11229


Ignore:
Timestamp:
Nov 9, 2020 10:03:05 PM (11 months ago)
Author:
dkocher
Comment:

Thanks for reporting this issue.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #11229

    • Property Status changed from new to assigned
    • Property Summary changed from AWS S3 AssumeRole doesn't use the external_id value to AssumeRole doesn't use the external_id value
    • Property Milestone changed from to 8.0
    • Property Owner set to dkocher
    • Property Type changed from defect to enhancement
  • Ticket #11229 – Description

    initial v1  
    11Hello,
    22
    3 CyberDuck fails to do an AWS IAM AssumeRole when trying to use S3 because it doesn't pass along the external_id value from the ~/.aws/credtential profile.
     3CyberDuck fails to do an AWS IAM AssumeRole when trying to use S3 because it doesn't pass along the external_id value from the ~/.aws/credential profile.
    44
    55I'm using CyberDuck to access AWS S3 resources using an AssumeRole action.  I would like to be able to use the external_id enforcement as suggested by AWS https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user_externalid.html