Failed to store token in OS password management system

Vega Open Beta Q&A
1

Active SDK Version: 0.24.12112
Vega CLI Version: 1.3.4

Attempting to authenticate using vega devmode login. The browser automatically opens with the code to complete authentication but after selecting allow I get the following message:

Error: Failed to save authentication token: failed to save access token data: failed to unlock correct collection ‘/org/freedesktop/secrets/aliases/default’: failed to store token in OS password management system

vega

3

Hello @antics ,

Our team is check on this issue.
We will provide an update soon.

Thanks,
Rohit

4

Hi @antics,

Thanks for the report and the screenshot. The key part of your error is:

failed to unlock correct collection ‘/org/freedesktop/secrets/aliases/default’

This tells us the login itself succeeded — the browser flow and token exchange worked — but the CLI could not save the token because your machine’s OS credential store (the freedesktop Secret Service, e.g. GNOME Keyring / KWallet on Linux) could not be unlocked. The CLI stores credentials only in the OS keyring (never on disk), so when the keyring is unavailable or locked, login can’t finish.

This is almost always an environment setup issue on the Linux side rather than a problem with the credentials themselves. A few things to try:

  1. Make sure a Secret Service provider is installed and running
  • Debian/Ubuntu: sudo apt install gnome-keyring
  • Fedora/RHEL: sudo dnf install gnome-keyring
  • KDE users can use kwalletmanager instead.

Then confirm the daemon is running for your session (for GNOME Keyring, gnome-keyring-daemon should be active).

  1. Ensure your default keyring exists and is unlocked
  • Open Passwords and Keys and check that you have a default keyring (often named Login).
  • If its password differs from your account password, it won’t auto-unlock at login. Right-click the keyring → Change Password and set it to match your login password so it unlocks automatically.
  1. If you’re on a SSH / WSL / container session - These environments often have no D-Bus session or unlocked keyring available. You’ll need to start a D-Bus session and unlock your default keyring before running vega devmode login.

To help us pin down the exact cause and give you precise steps, could you share:

  • Your Linux distribution and version
  • Desktop environment (GNOME, KDE, etc.) or whether this is SSH/WSL/container
  • Whether a keyring provider (gnome-keyring / kwallet) is installed

Thanks, Efren

6

Hi @antics,

Following up on this - just checking whether you had a chance to try the keyring setup steps above, and whether you’re still blocked.

If you’re still seeing the error, could you share the details Efren asked about so we can pin down the exact cause and give you precise steps:

  1. Your Linux distribution and version
  2. Your desktop environment (GNOME, KDE, etc.) - or whether this is an SSH / WSL / container session
  3. Whether a keyring provider (gnome-keyring / kwallet) is installed and running

Thanks,
Aishwarya