Disabling security for the cluster management console

The cluster management console is by default accessible over TLS. Enabling secure communication is highly recommended when integrity and confidentiality of data transmission is essential.

Before you begin

You must be a cluster administrator.

About this task

You can optionally disable security for the cluster management console.
Important: You must use the same security setting for the cluster management console and the RESTful web servers. If you disable security for one, you must also disable security for the other. This setting also takes effect for cloud bursting with host factory. Ensure that security for all these functions is configured consistently in the cluster; without a uniform configuration, errors occur. When security is uniformly enabled, you can use different certificates and keys as required.

Procedure

  1. Stop the WEBGUI service: 
    egosh service stop WEBGUI
  2. Copy server_gui.xml.nonssl to server_gui.xml:
    • Linux®: $EGO_CONFDIR/../../gui/conf/
    • Windows: %EGO_CONFDIR%\..\..\gui\conf\
    Important: Check for port conflicts in server_gui.xml. Ensure especially that the HTTP port is free and not used by any other service. The HTTP port (specified in the httpPort attribute) for the WEBGUI is by default 8080.
  3. Start the WEBGUI service: 
    egosh service start WEBGUI

Results

The cluster management console is now accessible over HTTP on the default port 8080. For example: http://myhostname.example.com:8080/platform.