Bug #109687 Using a custom SSH_AUTH_SOCK for ssh tunneling
Submitted: 18 Jan 2023 17:33 Modified: 19 Jan 2023 3:30
Reporter: Jay Janssen Email Updates:
Status: Verified Impact on me:
None 
Category:Shell VSCode Extension Severity:S4 (Feature request)
Version:8.0 OS:MacOS
Assigned to: CPU Architecture:Any

[18 Jan 2023 17:33] Jay Janssen 
Description:
My environment uses a custom SSH config and a custom SSH agent to handle the keys for ssh connections to my jumphost -- that is, the servers I use for ssh tunneling with mysql shell. 

In MySQL shell itself, I was able to simply change my SSH_AUTH_SOCK environment variable and I am able to tunnel properly there.  

However, this does not seem to be possible with the VS code plugin.  

One obvious issue is that the plugin requires the 'SSH Private Key file' to be populated (and it defaults otherwise).   There is actually no key file on disk, the agent handles it entirely.  

Secondly, I'm surmising the plugin is not paying attention to my SSH_AUTH_SOCK, though that's a guess.

I've tried a custom ssh config file that sets the IdentityAgent flag, but that doesn't work.   

The output channel for the plugin just states:

ERROR: Authentication error opening SSH tunnel: Access denied

How to repeat:
kind of tricky
[19 Jan 2023 3:30] MySQL Verification Team 
Hello Jay Janssen,

Thank you for the feature request!

regards,
Umesh