Hi all.
I am using an SFTP action in an action list wich I reuse a lot (to avoid having passwords everywhere in the FB solution). So my server is set by an action list parameter and varies a lot. The action list connects, do stuff and disconnects at the end. When it tries to connect to another server (when the action list is called again), the key in the cache is not rebuilt and fails the SFTP actions has it cannot authenticate correctly.
So basically, when you have an SFTP Connection that uses a variable as server and cache the publick key, the SFTp actions will fail when beeing called from a newly connect "SFTP connection" of the same name.
Required to fix (well I think
Thanks Jonathan,
I’ve checked in a fix that makes sure the cached public key is cleared when the connection is disconnected, I’ll let you know when the new build is available.
Regards,
Paul.
Hi Jonathan,
Could you please try the following build and let us know whether the issue is resolved?
URL: https://www.finalbuilder.com/downloads/finalbuilder/630/FB630_1865.exe
Regards,
Paul.
I installed and try the fix but sadly it had no effect. I attached the log ; search for "Connected to vmstg"
The first passed correctly and the message said "key cached".
The second did not passed at the SFTP upload. The connect said "key validated".
I think, for it to work, we should see a "key cached" in the second message as well. They value is also the same in the 2 connects.
Don't rush on it as I did find a bypass for my situation.
Thank you and have a happy new year ! Eway_-_2010.01_-_20091231104050.zip (335.482 KB)
Hi Jonathan,
I’ve had a bit more of a look and think about this problem and the issue is that it doesn’t make any sense to have the ‘Cache Public Key’ option enabled when using the Connect action like you are (called multiple times in the same project). As the cache option simply sets the ‘Server Public Key’ property of the action to the key so that subsequent runs of the project validates that the key is the same as the last time the server was connected to.
The solution is to simply disable the caching, and/or specify the server and expected server public key on each iteration.
Regards,
Paul.
Ok thanks, I was a little bit confused on this feature.