times

vSphere Client SDK 7.0 Update 2 | 9 March 2021 | Build 17638412

Check for additions and updates to these release notes.

Overview

The vSphere Client 7.0 U2 SDK enables development of vSphere Client plugins supported on both vSphere and VMware Cloud on AWS.

What's New

This release of the vSphere Client and the SDK introduces the following improvements:

FIPS compliance - vSphere Client 7.0 Update 2 is FIPS compliant and plugins are recommended to follow FIPS guidelines too. See Preparing Local Plug-ins for FIPS Compliance document for more information.
Plugin download retry mechanism - The plugin download URI might be temporarily unavailable when requested by the vSphere Client. In such cases the vSphere Client will attempt to download the plugin again a number of times at increasing intervals.

7.0 Update 2 release contains no changes to the vSphere Client API for plugins.

Resolved Issues

The multi-manifest of the SDK Remote plugin sample is not compatible with 6.7.

Remote plugin sample allows registration of a multi-manifest zip with both 7.0 and 6.7 manifests but fails to deploy on 6.7.

Fix: The plugin.json manifest of the Remote plugin sample has been fixed. The plugin multi-manifest is now compatible with both 6.7 and 7.0.

Known Issues

Two portlets in the same plug-in cannot share the same URL.

When a vSphere Client plug-in contains two portlets, they must specify different values for their attributes. Otherwise, a global refresh operation updates only one of the portlets.

Symptoms: Global refresh updates only one of the extensions having the same URL.

Workaround: Assign different URLs to the two portlets. For example:

   <extension id="portlet1">
          ...
                  <url>/vsphere-client/chassisa/resources/host-portlet1.html</url>
          ...
   </extension>
   <extension id="portlet2">
          ...
                  <url>/vsphere-client/chassisa/resources/host-portlet2.html</url>
          ...
   </extension>

Memory leak with Microsoft Internet Explorer 11.

vSphere Client's memory consumption increases steadily when using Microsoft Internet Explorer 11 with iframes in vSphere Client plug-ins. This is a known general issue with iframes on Internet Explorer.

Symptoms: Memory increases on IE11 with each opened plugin iframe leading to OutOfMemory error after some time.

Workaround: Use other browsers supported with the vSphere Client, such as Chrome or Firefox. List of supported browsers includes Microsoft Edge version 38 and later, Google Chrome version 50 and later, and Mozilla Firefox version 45 and later.