Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable multi-factor authentication to access amazon S3 / password logon for Cyberduck? #5483

Closed
cyberduck opened this issue Nov 30, 2010 · 3 comments
Assignees
Labels
enhancement s3 AWS S3 Protocol Implementation worksforme

Comments

@cyberduck
Copy link
Collaborator

cisk created the issue

You recently introduced multi-factor authentication to delete files on amazon S3.

Can you introduce multi-factor authentication to actually access the amazon S3 account in the first place?

i.e. you have to enter the unique code generated by the gemalto fob each time you access your S3 account/bucket?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

To my knowledge MFA is only available for login to the console or deleting files but not for logins using the API.

@cyberduck
Copy link
Collaborator Author

cisk commented

If this is not possible, would it be possible to add a password to gain access to Cyberduck?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:2 cisk]:

If this is not possible, would it be possible to add a password to gain access to Cyberduck?

You can move the credentials of your S3 account stored in your login.keychain (by default when choosing to save the password in the login prompt) to another keychain that you lock by default and give a separate password to access. Upon connecting, Cyberduck will ask to unlock that keychain.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement s3 AWS S3 Protocol Implementation worksforme
Projects
None yet
Development

No branches or pull requests

2 participants