Anything with SSH Changed Recently, Specifically Agent Forwarding?

Updates:

- Tried reverting to 2020.1.2 and 2020.1.1 and behavior did not change so not likely tied to an update.

- Tried a scorched earth approach:

• disabled the Setting Sync
• deleted from /Applications
• deleted all pycharm and jetbrains directories from /Application Support/. as per docs
• https://www.jetbrains.com/help/pycharm/uninstall.html
• https://www.jetbrains.com/help/pycharm/2019.3/tuning-the-ide.html#configure-platform-properties
• deleted the .idea/ dir from my project
• deleted .pycharm_helpers on the remote host

Re-installed pycharm, setup remote server connection, using OpenSSH and Agent.   Still have the same issue.   So...I dunno

Turning on some debug stuff It looks like pycharm is picking up the right stuff:

2020-07-09 15:18:08,932 [ 11751] INFO - z.sshj.transport.TransportImpl - Client identity string: SSH-2.0-SSHJ_0.27.0
2020-07-09 15:18:08,947 [ 11766] INFO - z.sshj.transport.TransportImpl - Server identity string: SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.1
2020-07-09 15:18:09,087 [ 11906] INFO - om.intellij.ssh.impl.sshj.sshj - Authentication log: SSH connection to chip@netman-new:22
* With overridden host from OpenSSH config: 192.168.0.5
* Compression methods from config: none
* With signature factories: ssh-rsa, ssh-dss, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521, ssh-ed25519
* With keep alive interval 120 seconds
* With keep alive count max 3
* With OpenSSH-like host key verifier (knownHostsFile=[/Users/cgwyn/.ssh/known_hosts], strictHostKeyChecking=ASK, hashKnownHosts=false)
* With identity from OpenSSH config {/Users/cgwyn/.ssh/id_rsa.priv.home, without passphrase}
* With 2 identities from ssh-agent[/private/tmp/com.apple.launchd.J4lebD0VwD/Listeners]
* With authentications allowed by the client: publickey, publickey, publickey, password, keyboard-interactive
* Connected
=> none (failure, new auth methods allowed by the server: publickey, password)
=> publickey /Users/cgwyn/.ssh/id_rsa.priv.home (success)

However if I start a Python Console on the remote host (from within pycharm)

for k, v in os.environ.items():
... if 'SSH' in k:
... print("{} --> {}".format(k, v))
... 
SSH_CONNECTION --> 192.168.0.240 56753 192.168.0.5 22
SSH_CLIENT --> 192.168.0.240 56753 22
SSH_TTY --> /dev/pts/1

There's no "SSH_AUTH_SOCK", not sure why it's not able to work with the agent to forward keys.

I have the exact same issue. Suddenly cannot debug code in a professional setting. Major blocker.

Any update on this? I am facing the same issue.

Hello, 

First of all, please vote for the corresponding feature request https://youtrack.jetbrains.com/issue/PY-45347 in order to increase its priority. 

As a possible workaround, please check the SSH_AUTH_SOCK in terminal and add it to Run/Debug Configuration environment variable section manually. 

Another workaround is to set the correct value for $SSH_AUTH_SOCK in a way so that it would be seen by all applications started from your Desktop session. For example, see this discussion: https://stackoverflow.com/questions/135688/setting-environment-variables-on-os-x

There is no workaround for the case where SSH_AUTH_SOCK changes dynamically, unfortunately.

I'm not sure the feature request captures the issue.

The issue appears to be PyCharm does not seem to honour ForwardAgent setting in SSH config.

Thus an available agent on my dev box is used to authenticate my SSH Interpreter, however the SSH agent is NOT passed to the SSH interpreter session - which is crucial.  Thus when I try to do a second SSH-hop from there it fails:

error authenticating: no auth sock variable

dev box [PyCharm] -> remote SSH interpreter -> 3rd box used by my python script

The problem is not the dynamic nature of SSH_AUTH_SOCK on the dev box, this should stay relatively static (in my case) - however Agent Forwarding dictates that a new auth sock is created on EACH run of the remote SSH interpreter *on the remote interpreter box*.  This is not happening in PyCharm despite my SSH config specifying "ForwardAgent yes".

If I do this from a regular linux console it works without issue.

To demonstrate the problem I can replace my remote interpreter with a bash script that echos out the value of the auth sock before executing python:

#!/usr/bin/env bash
echo "Auth Sock: *${SSH_AUTH_SOCK}*" >&2
python3 "$@"

PyCharm log gives us:

10:43 AM Couldn't refresh skeletons for remote interpreter
failed to run generator3/__main__.py for sshConfig://foo.bar@myserver:22 agent/home/foo.bar/pycharm-python, exit code 1, stderr: 
-----
Auth Sock: **

As you can see no value is propagated.  Now if I run the same thing from a console window:

But from a terminal it's fine:

$ ssh myserver /home/foo.bar/pycharm-python
Auth Sock: */tmp/ssh-hcaJgwmSUH/agent.43465*

This value will be different with each run, by design.

I don't consider this a feature request - it's a bug - PyCharm SSH is obeying some (eg Host), but not all the config (eg ForwardAgent) of SSH Client Config, and these exceptions are not explained in the documentation.

Thank you for clarification. I do agree this issue should be treated as bug. Could you please submit a bug report to our issue tracker at https://youtrack.jetbrains.com/issues/py ?

Thanks - this is done:

https://youtrack.jetbrains.com/issue/PY-49182