I have a Powershell script which runs winscp.com and supplies a number of arguments, including login details for an FTPS account on a remote server. When I use the GUI to connect to the account, it works correctly but originally gave me an error message stating the server's certificate was not known and asking me to continue, to which I said yes. It appears to have remembered my preference and connects successfully each time.
When I use my Powershell script to run winscp.com using the same login details, the same error message appears in my log each time, to which winscp.com times out and chooses not to proceed as it doesn't know the certificate is valid.
Can someone point me to why the winscp.com aspect of the application wouldn't remember the certificate if I had chosen to proceed within the GUI? I have checked that the fingerprint of the certificates are exactly the same and the user running both the gui and the script is the same.
Thanks in advance for your help and time.