Toad World® Forums

Automation: Secure FTP using Private Key


#1

I think there may be a bug with TDA’s implementation of the Secure FTP Connection with Public key only (not Public + Password).

Despite setting the “Authentication” drop-down to “Public Key”, and supplying the “Private key file” in the appropriate place, testing the connection still prompts for a password (which in my case is blank). The test is successful, all is well.

But when I try to use that FTP connection in the Automation FTP step, it will not allow me to select any file operations because it says a password is required - despite having checked “Save password” on the connections property, and leaving the box blank when prompted and hitting ok.

We really need this feature, so if there’s a work around here or some way to get it to work, that would really be awesome.


#2

Apologies for the wait, we will look into this first thing tomorrow.


#3

Thank you for your patience. We are still researching this.


#4

Do you have any more information? We need to use this function come Monday to upload a client list to an external vendor, and this is the only option (SSH over FTP via Pub/Pri key) that we have to complete the transfer.


#5

I am sorry, we are still looking into this, but we do not have any more information so far.


#6

We figured out that there is a bug in Ftp Automation activity validator that forces password submitting. I created a CR103344 to track the issue.

If it still actual, you can transfer the file using FTP document window b/c it does not contain the bug.

Sorry for the inconvenience,

Igor.


#7

Well unfortunately we need to automate the transfer process, and since it won’t save, that won’t work.

If there was a way to pass variables off from TDA to an outside script (ie. powershell, etc.) I might be able to work something out there.


#8

You could use the variable in an automation script in a find and replace. This file can then be used in the run command. The run command runs any command line util.

Debbie


#9

Yes, but so far as I know, there’s no built-in variable that captures the exported file name, and I haven’t figured out a way to define a variable that consists of both static as well as dynamic components (such as a static file name with a variable date).


#10

Path names can use variables in the name. Such as

c:\temp\myUniqueName#VARValue#.txt

I also assume you could take a var and set the value to the whole path. However, I have never tried this.

Debbie


#11

The Toad automation Run program works very well with dynamic names. You can use it for any program that takes parameters in a command line argument by inserting #variable_name# where you need it. The run program has an argument line for where you would put the space and parameters (no space needed) after the program being executed. I used this to get around the problem of the Toad copy function causing a build error for a file that does not exist at run time but will exist later on in the job and has a datestamp added to the file name. I pass the dynamic file name to a batch job that I created. The Toad copy problem already has a CR and might be fixed in 3.2 but I am still on 3.1.


#12

Hi, Sorry to bring up an old thread however was this ever resolved.

I’m using a tda 3.7 and am using a private key file without a password but still being asked for a password.


#13

I don’t have access to a FTP server with this type of authentication to check out the current behavior of the TDP 3.8 but I’d suggest to use it because there have been several updates to the FTP.

Regards

Aleksey


#14

I’m in TDP 4.3 and this is still an issue. Of note…I did get around it by setting it to Public Key + Password, putting random characters into the password field, setting it back to Public Key and saving.


#15

I am in 4.3 and this is still an issue


#16

check TDP4.3 and it is an issue, create QAT-13338 to bring it up to developer