AWS SSO Connect to Identity Center(OIdC) with CyberDuck #16023
Unanswered
arstrandsr
asked this question in
Q&A
Replies: 1 comment
-
In #13377. The problem is that AWS SSO (Identity Center) is not OIDC compliant and therefore does not work without AWS CLI. Setups that use an external OIDC provider are supported with #13804. You can read about it on our blog 1. The setup with AWS SSO is supported using the S3 (Credentials from AWS Command Line Interface) profile 2 connection profile. Configure a bookmark with the field titled Profile Name matching the profile name from ~/.aws/credentials. You will need to make sure to login using AWS CLI with
Footnotes |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a working OIdC connection via AWS CLI to AWS SSO (Identity Center). Now I need to give the "credentials" to Cyberduck. The Credentials are in the
.aws/config
file as shown below.I am looking for ideas/suggestions.
Background
AWS, and I believe others are moving to Open Identity Connector SSO. AWS has named the SSO offering Identity Center. Identity center uses short term STS tokens exclusively.
The goal
Connect Cyberduck to my AWS S3 bucket.
Tried steps
None of the options seem to look anything like the required AWS connection sequence. The below
.aws/config
file works with AWS CLI and automatically refreshes tokens.Idea Requests
.aws/config file
Items like
<S3Bucket>
were manually edited here for security.Beta Was this translation helpful? Give feedback.
All reactions