Enhancements

  • Introduced a command line parameter (hazelcast.mc.forceLogoutOnMultipleLogin) to enable/disable forced logout on multiple login attempts with the same user name. [#629]
  • Password complexity rules have been hardened. [#621]
  • Introduced a global error page for unhandled exceptions. [#620]
  • Time travel is no longer allowed for the clusters whose names include non-alpha-numeric characters other than dash (-) and underscore (_). A warning is shown to the user if time travel is enabled such clusters. This enhancement was needed since by having special characters in the cluster name, one can traverse the filesystem and cause harm. [#608]
  • Management Center is now compatible with Java 9; it was not working under JDK9. [#538], [#600]
  • The session timeout has been made configurable for the embedded mode. It was by default 30 minutes. [#461]

Fixes

  • Upon the very first startup of Management Center, after entering the license, when a cluster with WAN replication enabled is viewed, the "WAN" tab is not shown. It is only shown after the user logs in again. [#637]
  • Cache browser does not work for records on remote member: when Management Center tries to get a cache entry, execution fails if the record is not available locally on the member. [#603]
  • Even if the license key is provided during the initial configuration, the warning line "Node Limit Exceeded" is still shown in Management Center. [#564]
  • Management Center's "Map Config" dialog shows "default" as the map name although it is not "default".[#501]
  • The session ID must be updated after logging into Management Center. [#463]
  • Multiple simultaneous logons must not be allowed using the same user ID as a security requirement. [#462]
  • The error messages shown to the end users are not sanitized: In these messages, Management Center should reveal only the information that the end users need to know. [#460]
  • The "Operations" dropdown menu does not show the options after a license update. [#396]

Behavioral Changes

  • Default value of the system property hazelcast.mc.max.visible.instance.count changed from 100 to Integer.MAX_VALUE. So you may see more than usual data in your Management Center, if you have more than 100 data structures in your Hazelcast cluster.