Unable to connect with SSH certificate

[buzzia2001]

Hi everyone,
I'm trying to setting up vs code in order to connect to my I whith certificate. Now a days I'm still using password, but I want to try using certificate. My version of code4i is 2.13.6 and my vs code is 1.95.3 on MacOS.
When I setup up my connectio I choose my idrsa.pub and when I click on save it seems to be fine, but when I try to connect there is this error "config.privateKeyPath does not exist at given fs path"
Can anyone help me?
Thank you a lot for your amazing job

Andrea

[sebjulliand]

Hi @buzzia2001 ,
there may be bug when the Login editor saved the private key path.

As a workaround, open your user settings as JSON, look for your connection settings, and then put the privateKeyPath like this:

Save and try to connect.

Also, make sure you put the path to your private key (presumably id_rsa or id_ed25519), and not the .pub file which is the public key.

[buzzia2001]

Ciao @sebjulliand,
editing my conf works fine.
As you can see there were some trash on my config file... As you said I think it's a bug of login editor

[sebjulliand]

Yep, this will corrected in the future.

[buzzia2001]

@sebjulliand thank you for your support

[sebjulliand]

@sebjulliand thank you for your support

Anytime 😉

[jwoehr]

There definitely is a bug in creating a connection lately. I just tried for a while and had to edit the settings in json.

[worksofliam]

@jwoehr you mean in regards to using a certificate?

We have a PR in the works. Just needs a little more testing.

[jwoehr]

It's that it doesn't correctly create the entry in the settings.json file.
Or at least it did not do so for me today @worksofliam

[worksofliam]

@jwoehr if you create a new connection and attempt to connect, it won't save unless it connects successfully.

[jwoehr]

It didn't seem to save the path to the key file correctly. It just put the file name in with no path.

[jwoehr]

@worksofliam here's what's happening today when I try to create a new IBM i connection.

When I get to the "private key" part, my Ubuntu-like distro opens a Gnome requester and I choose the key from my home ~/.ssh directory. In the VSCode dialog, I only see the name of the key, no path attached.

Then I try to connect and get this error:

If I look at ~/.config/Code/Users/settings.json I find:

{
            "name": "SomeHost",
            "host": "192.168.1.99",
            "port": 22,
            "username": "MYPROFILE"
            "privateKeyPath": "undefined"
        }

If I manually thereafter edit the file to add the privateKeyPath, all works as expected.

[jwoehr]

@worksofliam Just had another one this morning ... customer who couldn't get private key login working, this time on Windows. Same thing: Browse for private key, shows correct in the settings dialog, but ends up with "privateKeyPath": "undefined". Edited settings.json manually and it works.

[sebjulliand]

@jwoehr this is known bug. The Choose file button from the connection editor used to return the full path to the selected file, but since what I suspect to be a recent VS Code update, the full path isn't returned anymore. Instead you either get a fake path or undefined.

We'll try to release a fix at some point, but for now the only workaround is to edit the settings manually and set the path to the private key manually 😑

[jwoehr]

Je vous en remercie ... just wanted to make sure we are clear on what users are experiencing.

[sebjulliand]

Je vous en remercie ... just wanted to make sure we are clear on what users are experiencing.

Avec plaisir ! Yup, users are experiencing an unexpected annoying surprise feature.