topic Re:Https back-end problems in vSphere Client SDK Discussions

Https back-end problems

ilyak — Sun, 03 Dec 2017 08:54:53 GMT

Our plugin performing https requests to the back-end server.

According to the SDK samples, we can implement ThumbprintTrustManager/ThumbprintHostNameVerifier in order to be able to make requests to the https server with self signed certificate. But how can it work, if the web client has multiple plugins which have ThumbprintTrustManager? It seems that all plugins are running in the same VM, so calls like "HttpsURLConnection.setDefaultSSLSocketFactory(sc.getSocketFactory());" will influence not only our plugin but other plugins, too.

Re:Https back-end problems

_vladi_ — Tue, 05 Dec 2017 12:57:18 GMT

Hi,

Thank you for the report.

Plugins are running in the same VM but they are loaded by different class loaders. In the case when a class is being provided by the HTML Client you can:

- switch to using non-static calls (as mentioned in the documentation https://docs.oracle.com/javase/7/docs/api/javax/net/ssl/HttpsURLConnection.html) OR

- embed your own version of the library in the Bundle-Classpath of your service jar bundle.

We should definitely look into a better sample that takes into account this perspective.

Cheers,

Vladi

Re:Https back-end problems

ilyak — Wed, 06 Dec 2017 09:40:46 GMT

Thank you for your reply. Very helpfull.

As far as I understand calling to

VimPortType.findExtension can be done only via static calls (In case my vCenter has only self signed certificate)