The current jsch library we use does not support ssh keys generated by OpenSSH 7.8+ (which has -----BEGIN OPENSSH PRIVATE KEY----- instead of the previous -----BEGIN RSA PRIVATE KEY-----), and so an invalid privatekey error will occur. As described with resolutions provided in https://stackoverflow.com/questions/53134212/invalid-privatekey-when-using-jsch.
I'd propose to update library to a fork https://github.com/mwiede/jsch instead. First attempt with new library worked locally, however, it failed to authenticate with the SSH tunnel in Tableau connector, so additional investigation will be needed around that.
You will encounter a private key error if you use the SSH tunnel via the driver or Tableau connector (instead of using command line) with a .pem file generated by OpenSSH 7.8+ (i.e. starts with -----BEGIN OPENSSH PRIVATE KEY-----)
Describe the bug
The current jsch library we use does not support ssh keys generated by OpenSSH 7.8+ (which has
-----BEGIN OPENSSH PRIVATE KEY-----instead of the previous-----BEGIN RSA PRIVATE KEY-----), and so aninvalid privatekeyerror will occur. As described with resolutions provided in https://stackoverflow.com/questions/53134212/invalid-privatekey-when-using-jsch.I'd propose to update library to a fork https://github.com/mwiede/jsch instead. First attempt with new library worked locally, however, it failed to authenticate with the SSH tunnel in Tableau connector, so additional investigation will be needed around that.
Steps to Reproduce
.pemfile generated by OpenSSH 7.8+ (i.e. starts with-----BEGIN OPENSSH PRIVATE KEY-----)Expected behavior
Screenshots
Environment
Additional Context