-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Open
Labels
Description
Describe the bug
There are two bugs:
- the documentation https://docs.github.com/en/copilot/how-tos/copilot-cli/set-up-copilot-cli/troubleshoot-copilot-cli-auth#keychain-access-failure is wrong. Under Ubuntu (see below for version), If
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) - Once
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 help
Affected version
GitHub Copilot CLI 1.0.9
Steps to reproduce the behavior
- Make sure
secret-toolis installed, by runningcommand -v secret-tool: - start Copilot CLI by running
copilot - login with
/login(in my case, this requires quite a few clicks since I use the SSO login of my organization) - Copilot CLI complains that
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 fix
Expected behavior
When secret-tool is installed and I run copilot, then /login, Copilot CLI should be able to see secret-tool and 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 instead
Additional context
Linux version:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04.1 LTS
Release: 24.04
Codename: noble
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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Type
Fields
Give feedbackNo fields configured for Bug.