961dcb7 created the issue

CyberDuck doesn't support assume role functionalities of AWS.

So it means that accessKeyID and accessToken from centralised authentication
account can't be used to access a bucket in a different account.

AWS Sdks and aws cli for example support profiles nicely and more and more programs does it too.
ex:

awscli -profile "accountprod"

awscli -profile "accountperf"

Would be awesome if you could include this functionality, its actually part of AWS best practises.
Basically , one checkbox to activate profile, and if checked, a new textbox to specify the profile that are usually stored in
.aws/credentials

example:

[default]
aws_access_key_id = AKIA....
aws_secret_access_key = 

[profileprod]
region=us-east-1
role_arn=arn:aws:iam::1234567890:role/cross-account-access
source_profile=default

[profileperf]
region=us-east-1
role_arn=arn:aws:iam::0987654321:role/cross-account-access
source_profile=default

[profiletest]
region=us-east-1
role_arn=arn:aws:iam::010203040506:role/cross-account-access
source_profile=default

Thanks a lot.