Add cli for setting and unsetting credentials to system keyring#14896
Closed
jtfmumm wants to merge 15 commits intojtfm/keyring-explorationfrom
Closed
Add cli for setting and unsetting credentials to system keyring#14896jtfmumm wants to merge 15 commits intojtfm/keyring-explorationfrom
jtfmumm wants to merge 15 commits intojtfm/keyring-explorationfrom
Conversation
9011c3b to
5f28e9e
Compare
jtfmumm
commented
Jul 25, 2025
| url: &DisplaySafeUrl, | ||
| username: &str, | ||
| ) -> Result<(), uv_keyring::Error> { | ||
| if let KeyringProviderBackend::Native = &self.backend { |
Contributor
Author
There was a problem hiding this comment.
We could warn here if this is not set.
jtfmumm
commented
Jul 25, 2025
|
|
||
| #[derive(Args)] | ||
| pub struct AuthUnsetArgs { | ||
| /// The authentication service to configure |
Contributor
Author
There was a problem hiding this comment.
This needs to be fleshed out more once we've decided how we're presenting the service
jtfmumm
commented
Jul 25, 2025
|
|
||
| #[derive(Args)] | ||
| pub struct AuthSetArgs { | ||
| /// The authentication service to configure |
Contributor
Author
There was a problem hiding this comment.
This needs to be fleshed out more once we've decided how we're presenting the service
jtfmumm
commented
Jul 25, 2025
| @@ -0,0 +1 @@ | |||
| pub(crate) mod configure; | |||
Contributor
Author
There was a problem hiding this comment.
At first I thought this would need to be split out, but I'll probably update this to use just commands/auth.rs
5f28e9e to
3be17ea
Compare
3be17ea to
5280823
Compare
f8756ea to
166e9e1
Compare
166e9e1 to
496c7a2
Compare
d1ab06b to
a2df725
Compare
5280823 to
63be74d
Compare
a2df725 to
a898fe4
Compare
80154a2 to
ec49f65
Compare
zanieb
added a commit
that referenced
this pull request
Aug 28, 2025
Picks up the work from - #14559 - #14896 There are some high-level changes from those pull requests 1. We do not stash seen credentials in the keyring automatically 2. We use `auth login` and `auth logout` (for future consistency) 3. We add a `token` command for showing the credential that will be used As well as many smaller changes to API, messaging, testing, etc. --------- Co-authored-by: John Mumm <jtfmumm@gmail.com>
zanieb
added a commit
that referenced
this pull request
Aug 29, 2025
Picks up the work from - #14559 - #14896 There are some high-level changes from those pull requests 1. We do not stash seen credentials in the keyring automatically 2. We use `auth login` and `auth logout` (for future consistency) 3. We add a `token` command for showing the credential that will be used As well as many smaller changes to API, messaging, testing, etc. --------- Co-authored-by: John Mumm <jtfmumm@gmail.com>
zanieb
added a commit
that referenced
this pull request
Aug 30, 2025
Picks up the work from - #14559 - #14896 There are some high-level changes from those pull requests 1. We do not stash seen credentials in the keyring automatically 2. We use `auth login` and `auth logout` (for future consistency) 3. We add a `token` command for showing the credential that will be used As well as many smaller changes to API, messaging, testing, etc. --------- Co-authored-by: John Mumm <jtfmumm@gmail.com>
zanieb
added a commit
that referenced
this pull request
Aug 31, 2025
Picks up the work from - #14559 - #14896 There are some high-level changes from those pull requests 1. We do not stash seen credentials in the keyring automatically 2. We use `auth login` and `auth logout` (for future consistency) 3. We add a `token` command for showing the credential that will be used As well as many smaller changes to API, messaging, testing, etc. --------- Co-authored-by: John Mumm <jtfmumm@gmail.com>
Contributor
Author
|
Closed in favor of #15539 |
zanieb
added a commit
that referenced
this pull request
Sep 2, 2025
Picks up the work from - #14559 - #14896 There are some high-level changes from those pull requests 1. We do not stash seen credentials in the keyring automatically 2. We use `auth login` and `auth logout` (for future consistency) 3. We add a `token` command for showing the credential that will be used As well as many smaller changes to API, messaging, testing, etc. --------- Co-authored-by: John Mumm <jtfmumm@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a work in progress that depends on #14559. There are still open design questions.
There are a couple of FIXMEs in this draft PR. Some are for more doc details, but a few are about adding support for accepting passwords over stdin and providing a security warning if the user passes a plaintext password to a
--passwordoption.Also left to do:
/simplefrom a service before persisting credentials.--previewflag, unless we think it's enough that you must explicitly configure anativekeyring provider (we've discussed making it the default, but that's not the behavior here)