topic Re: SFTP Web connector error in Connectivity & Data Prep

SFTP Web connector error

mattdetwiler — Tue, 08 Nov 2022 22:45:05 GMT

I'm trying to connect to an SFTP data source with a private key and passphrase. I think everything is good but I'm getting the following error: "There was an Error running the table (status code - 500. A public key corresponding to the supplied private key was not accepted by the server or the user name is incorrect)

The user name is working on other systems just fine and I don't see anywhere where I can load the public key. I've tried to check the "Allow self signed" option and that doesn't seem to be working.

Re: SFTP Web connector error

Jay_Brown — Mon, 14 Nov 2022 22:24:07 GMT

Hi @mattdetwiler ,

The Public key should be in place on the SFTP server. You'll need to use the Private key file on the server that is hosting WebConnectors, then provide that info in the entry for Path To Private Key File.

It's been a while since I tested but I believe if you have the key for 'User1', e.g. 'user1.pub', you would put it somewhere reachable such as 'D:\Keys' and then use the path as D:\Keys\user1.pub for that user.

Edit: I just tested this and :

Using PuttyGen,I created a new key pair and got the passphrase.
I then created my user at the SFTP site and uploaded the public key for that user.
I moved the private key to my WebConnectors server in C:\Temp\Keys.
I went back to WebConnectors UI and it worked using "C:\Temp\Keys\private.ppk" in the Path To Private Key File field, and manually entering my passphrase.

I hope that helps!

Re: SFTP Web connector error

mattdetwiler — Mon, 14 Nov 2022 22:27:53 GMT

Ok I have the private key in a folder that is allowed to the web connectors but it is giving me that error. My devops team says they are able to connect to the SFTP server from that machine.

It feels like either Qlik is expecting me to use a password or maybe that the format of the key isn't what Qlik is expecting. We are currently using a .pem format for Oracle Integration Services.

Re: SFTP Web connector error

Jay_Brown — Fri, 18 Nov 2022 13:18:27 GMT

Hi @mattdetwiler , when I set this up the passphrase was required. Did your DevOps team give that to you?

Re: SFTP Web connector error

mattdetwiler — Fri, 18 Nov 2022 19:05:19 GMT

I have a passphrase but not a password

Re: SFTP Web connector error

Jay_Brown — Fri, 18 Nov 2022 19:47:47 GMT

My lab environment works without a password for both download and upload. All I need is the Private Key file File and the passphrase that goes with it.

See the below config:

dc.domain.local is the internal lab box where I host my own SFTP server.
C:\Temp\Keys is where I have my private key file
1. note this is C:\ on the Web Connectors server not my client machine, if I had it on a file share I would use \\server\share
The Source location is where I have my file on the server.
Remote path is the remote path on the SFTP server.

Can you post an obfuscated screenshot of your config?

--J

Re: SFTP Web connector error

mattdetwiler — Fri, 18 Nov 2022 20:24:22 GMT

This is an SFTP site running on Azure server.blob.core.windows.net

-If I change the host name it fails differently so I think that's good
-If I remove the .containername.username from the username I get a different error so it's seeing that
-If I remove the passphrase it's erroring out so it sees that too

It's almost like the username and passphrase are wrong but this combo works fine connecting from Oracle.

The error in the Qlik log is:

Rebex.Net.SftpException: A public key corresponding to the supplied private key was not accepted by the server or the user name is incorrect. ---> Rebex.Net.SshException: A public key corresponding to the supplied private key was not accepted by the server or the user name is incorrect.
at Rebex.Net.SshSession.dxgpo(String p0, String p1, SshPrivateKey p2, SshGssApiCredentials p3, Boolean p4)

So it seems like it's getting an error back from the SFTP server.

Re: SFTP Web connector error

mattdetwiler — Fri, 18 Nov 2022 21:11:34 GMT

We were able to create a new user with just a username and password (no key/passphrase) and it seems to be working. We think what may have been happening is even though Qlik was set up correctly with the key maybe it wasn't being sent.

I'm also wondering if this is a bug with Qlik Web connectors and Azure blob storage/SFTP