Quantcast
Viewing all articles
Browse latest Browse all 6689

plink host key is not cached in the registry when run after publishing

I need a solution

Hello, I am using plink to run ls command. I am using "merge data" and "execute process and wait" components. Text in merge data is shown below

merge data: -ssh [Server_Name] -l [Username] -pw [Password] -no_in ls

And merge data is passed to arguments in execute process and wait component. 

When i run the workflow in debugging mode, it works fine as I want. But when the workflow is published on IIS7 it asks for server host key is not cached. Below is the error

"The server's host key is not cached in the registry. You have no guarantee that the server is the computer you think it is. The server's rsa2 key fingerprint is: ssh-rsa 2048 6c:18:12:e6:e5:cc:78:74:7a:b4:6d:07:70:9c:0e:c7 If you trust this host, enter "y" to add the key to PuTTY's cache and carry on connecting. If you want to carry on connecting just once, without adding the key to the cache, enter "n". If you do not trust this host, press Return to abandon the connection. Store key in cache? (y/n) Connection abandoned."

Is there any settings i need to set in IIS.

With my knowledge we can solve this by echo y which is shown below. But how can I handle this using Symantec Workflow.

echo y| plink -ssh [Server_Name] -l [Username] -pw [Password] -no_in ls

This will be very helpful if it is sovled. Thanks


Viewing all articles
Browse latest Browse all 6689

Trending Articles