-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Ubuntu keychain support is broken #2165
Copy link
Copy link
Open
Labels
area:authenticationLogin, OAuth, device auth, token management, and keychain integrationLogin, OAuth, device auth, token management, and keychain integrationarea:platform-linuxLinux-specific: Wayland, X11, Ubuntu, Fedora, Alpine, ARM, terminal emulatorsLinux-specific: Wayland, X11, Ubuntu, Fedora, Alpine, ARM, terminal emulators
Metadata
Metadata
Assignees
Labels
area:authenticationLogin, OAuth, device auth, token management, and keychain integrationLogin, OAuth, device auth, token management, and keychain integrationarea:platform-linuxLinux-specific: Wayland, X11, Ubuntu, Fedora, Alpine, ARM, terminal emulatorsLinux-specific: Wayland, X11, Ubuntu, Fedora, Alpine, ARM, terminal emulators
Type
Fields
Give feedbackNo fields configured for Bug.
Describe the bug
There are two bugs:
secret-toolis not installed, runningsudo apt install libsecret-1-0 gnome-keyring seahorsedoesn't install it. You also need to runsudo apt install libsecret-tools(please fix the docs)secret-toolis correctly installed, as confirmed bycommand -v secret-tool, Copilot-CLI still fails to findsecret-tooland use it. I tried to log out of my SSH connection to Ubuntu, log in again and try again: didn't helpAffected version
GitHub Copilot CLI 1.0.9
Steps to reproduce the behavior
secret-toolis installed, by runningcommand -v secret-tool:copilot/login(in my case, this requires quite a few clicks since I use the SSO login of my organization)The system vault (keychain, keyring, password manager, etc.) is not available. You may need to install one.So it actually doesn't seesecret-tool. Please fixExpected behavior
When
secret-toolis installed and I runcopilot, then/login, Copilot CLI should be able to seesecret-tooland safely store my token in the keychain, instead of prompting me to accept the risk and store the token in the plain text config file insteadAdditional context
Linux version:
I'm connecting to Ubuntu from Windows via SSH with the Windows Terminal. The remote Ubuntu server is a headless server, but I would expect a key manager to work (once installed) regardless of that