You have configured public key authentication from your CPI tenant to an SFTP server but the connection test returns the following error:
com.jcraft.jsch.JSchException: Auth Fail
I ran into this issue as well and found the underlying cause before I found this workaround, so I thought I'd submit a patch. As alluded to in the gist, JSCH does not know about jsch-agent-proxy and so it attempts to resolve keys as it would normally. In normal execution it expects a UserInfo implementation when it encounters an encrypted (password protected) private key. The code throws an Exception right off the bat if the UserInfo implementation doesn't exist and doesn't give the jsch-agent-proxy a chance to pull the keys from the ssh-agent. Below snippet from com.jcraft.jsch.UserAuthPublicKey#start lines 118-130:
It worked for me... almost. I was so happy finally getting the keygen converted (had to struggle with ACL on remote server where both NAS and SSH run) just to be even more disappointed having the same result in the end - key is rejected, whatever I tried (different file extensions - .pem and empty one, ssh-keygen or puttygen, empty passphraze and a complex one) thou password authentification works fine. Strangely enough, it seems like it needs zero time for Samsung Files to reject connection. I fear the problem is totally on Samsung client side.
aa06259810