Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

accounts with multiple secrets #14

Closed
notslang opened this issue Oct 13, 2014 · 4 comments
Closed

accounts with multiple secrets #14

notslang opened this issue Oct 13, 2014 · 4 comments

Comments

@notslang
Copy link

S3 has both an access key and secret key. How should I go about storing both of these in keytar?

@zcbenz
Copy link
Contributor

zcbenz commented Oct 14, 2014

You have to store them with different names like addPassword('S3', 'my_access_key', 'blabla') and addPassword('S3', 'my_secrect_key', 'blabla'). Not all systems have support for storing multiple secrets for one account, so keytar can not support it to keep cross-platform ability.

@zcbenz zcbenz closed this as completed Oct 14, 2014
@notslang
Copy link
Author

Thanks @zcbenz

@Jenius ☝️ - that should work for the cases where there are multiple secrets per deployer

@jescalan
Copy link

@slang800 no it won't because it's not supported cross-platform, as @zcbenz kindly mentioned. But that's an issue we can discuss in the relevant repo, not here.

@notslang
Copy link
Author

I think you misread that... @zcbenz's solution was for getting around the "1 secret per account" limit. He was saying that keytar doesn't have a more intuitive solution because of the cross-platform issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants