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
My credentials are not being read #11059
Comments
I find the exact same thing. Also Ubuntu Linux (18.04), duck 7.4.0. Credentials file contains an https string that has my credentials embedded in it, but I'm prompted every time. Also, @Maeglin, I don't see your "askubuntu" page, is the URL correct? |
However, I am able to specify credentials on the command line using the -u and -p options. (side note, I tried using -i and also using -i and both forms result in: "Login s3.amazonaws.com. Login failed. The AWS Access Key Id you provided does not exist in our records." I presume I misunderstand what -i is intended for?) |
My question on Stack Exchange was migrated to SuperUser https://superuser.com/questions/1556379/cyberduck-no-login-credentials-could-be-found-in-the-keychain-despite-being-th |
The -i flag is intended for an SSH key, the kind you generate with the command |
Please try to include the |
Replying to [comment:12 dkocher]:
But this makes no sense, you still have to put the access key in every request? |
Our implementations for saving the password in macOS Keychain, Windows Credentials Store and this plain file implementation require the lookup by username/access key. |
I've made a question on SuperUser just in case I get a resolution there: https://superuser.com/questions/1556379/cyberduck-no-login-credentials-could-be-found-in-the-keychain-despite-being-th
Please see it for details on this issue.
To summarise: I run
duck --list <s3 address here>
and it prompts for the key and pass which are supplied, I confirm to save my details and those details are stored in~/.duck/credentials
successfully with perms 664 with .duck perms 775 both owned by my user and the credentials appear to have been written successfully into the credentials file. But when I run a similar operation (in this case exactly the same request to list the dir), it prompts me again having told me it can't find the credentials.Listing directory path… Login s3.amazonaws.com. Login s3.amazonaws.com – S3 with username and password. No login credentials could be found in the Keychain. Access Key ID:
The text was updated successfully, but these errors were encountered: