Release: March 2017
New in this Release
-
Workaround for compatibility with Cisco UCS vSphere Web Client plugins
This release enforces TLS version 1.2 for plugin communications with a FlashArray. The Everpure vSphere Web Client Plugin 2.5.1 release contains a workaround to strictly enforce the usage of TLS version 1.2 for all communications between the Everpure vSphere Web Client Plugin and the FlashArray.
Why is this release necessary? When attempting to connect to a Cisco UCS server, the Cisco UCS vSphere Web Client Plugin resets the global Java Virtual Machine (JVM) TLS protocol options to 1.0. This setting forces all vSphere web client plugins installed on the vSphere server (including the Everpure vSphere Web Client Plugin) to use TLS version 1.0 for all secure communications to their respective appliances.
However, since TLS 1.0 is no longer a secure protocol, Purity versions 4.7.0 and higher do not support TLS 1.0. Therefore our previous vSphere Web Client Plugins (version 2.5.0 and earlier) cannot connect to a FlashArray running Purity version 4.7.0 or later. Plugin version 2.5.1 is required.
Notes:
-
Installation: The vSphere client plugin service may be unable to download the updated Everpure vSphere client plugin during the installation process. It may be necessary to disable the Cisco UCS plugin and restart the vSphere client plugin service on the vSphere server instance before the Everpure vSphere client plugin can be successfully downloaded and installed onto the vSphere server.
-
Other plugins: This workaround does not affect any other vSphere web client plugin installed on the same vSphere instance, meaning all other vSphere web client plugins can continue to use TLS version 1.0 for all communication.
-