That last thread mentions to just continue on without doing the forge login and that it works fine for them. As I’m starting out looking into developing something here, I think it would be in my best interest to have all the tooling working as intended.
As a last option I also followed an article to install the dev package of libsecret and build it. However, this also did not work for me. (sorry, no link, new account)
Interestingly, they key does show up in my Atlassian Account as having been used. That confirms that the login part at least is working and the problem is fully local.
If you have any other suggestions, I’m very much open to them!
Since you’re running WSL and not the full Ubuntu distribution, I believe the service responsible for secret storage (gnome-keyring-daemon or similar) isn’t running inside the Linux environment, and therefore Forge can’t store your token securely (it can’t use Windows’ secure storage from inside WSL either).
Sorry for the confusing message, we will investigate how to provide better diagnostics and store the token securely under WSL.
In meanwhile you can:
Use the environment variables and skip forge login. Make sure the script setting them up - or your shell history - is secured!
Install and use Forge under Windows directly if you are comfortable in that environment.
At your own risk, use one of the following solutions to run a keyring daemon inside WSL:
I got this working by installing some apt packages to get gnome keyring working. Can’t tell you exactly what I installed off the top of my head but next time I reset my environment I will let you know.
The gnome keyring actually works fine in WSL2 with the new X11 forwarding
Hi,
Using WSL2 with Windows 11, I have installed gnome-keyring package. I have also installed NVIDIA CUDA Support for WSL2 but I don’t think it is necessary. After that, I have restarted WSL (wsl --shutdown and later wsl) to get it working.
