Skip to content

username could default to the current (system) username #60

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

Closed
gaborcsardi opened this issue Oct 9, 2018 · 4 comments · Fixed by #100
Closed

username could default to the current (system) username #60

gaborcsardi opened this issue Oct 9, 2018 · 4 comments · Fixed by #100
Labels
feature a feature request or enhancement

Comments

@gaborcsardi
Copy link
Member

gaborcsardi commented Oct 9, 2018

At least in key_get(), maybe also on key_set().

@anssonliang
Copy link

have you solved the key_get() issue where username could default to the current system user?

@gaborcsardi
Copy link
Member Author

You mean this very issue? I guess I haven't, that's why it is still open.

@anssonliang
Copy link

Yes, it bugs me when working on appbot. Obviously If the username is included in the key_get(), the error is gone.

keyring::key_get("appbot_api", "SNxxxxxxBG")
[1] "d8xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxkS"

keyring::key_get("appbot_api")
Error in b_wincred_i_get(target) :
Windows credential store error in 'get': Element not found.

@gaborcsardi gaborcsardi added the feature a feature request or enhancement label Apr 23, 2021
@gaborcsardi
Copy link
Member Author

Well, this would make sense, but it is a breaking change at this point, because the username is optional for a key.

Instead, I can introduce an option, which you can set to opt in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature a feature request or enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants