vCenter Java and Perl API scripts stopped working after configuring vCenter for TLSv1.2

[blkolo_]

I run several monitoring scripts (that I inherited) from vMA appliances. We patched our vCenters with vSphereTlsReconfigurator-6.5 so it only listens using TLSv1.1 & TLSv1.2.

Now our scripts no longer connect using Java app "Remote host closed connection during handshake" or Perl scipt:"Server version is unavailable at https://servername:443/sdk/vimService.wsdl"

I suspect I need to update my SDKs - Any guidance on resolving? Guidance on updating SDK on VMware vMA?

[doskiran]

VMA:

-------

The vSphere Management Assistant 6.5 might fail to communicate with vCenter Server. This happens when vCenter Server instance is configured with TLSv1.1 or TLSv1.2 protocols. An error message similar to the following is displayed:

Connect to ServerIP failed with ssl error 0x1.

Workaround: Use an independent vSphere Command Line Interface 6.5. For more information, see the vSphere Command-Line Interface Concepts and Examplesand vSphere Command-Line Interface Reference.

Java SDK:

-------------

For java api to work , set "-Dhttps.protocols=TLSv1,TLSv1.1,TLSv1.2" in program vm arguments.