scripting issues in 3.1.3 CLI

[hdtvguy]

So the 3.1.3 CLI has some new behavior that can seriously impact any automated scripts you may be running unattended. When you run the CLI the first time against a given array you are prompted about the arrays certificate and the option to cache the certificate locally. Some issues arise with this; the first is if you upgrade to 3.1.3 CLI you automate scripts will fail until you cache the certificate. The second is the cached certificate on a Windows box is stored in a directory under the user account for the user accepting the certificate. As you can see this is very problematic for any type of automated scripting. The good news is so far you can use the 3.1.2 CLI against a 3.1.3 array so this avoids the issue in the short term.

[hdtvguy]

Found a work around. There are 2 ways to solve this. First is to add the -nosockssl to the command line. The other is to set a system variable of TPDNOSOCKSSL and set the value of that variable to a non-zero. If you plan on using the windows system account you need to reboot after setting that variable for the system account to pick up that change