Disabling security for the RESTful API web servers

The web servers that host the RESTful APIs are by default accessible over TLS. Enabling security 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 REST web server, which hosts the APIs for EGO resource management, package deployment, and SOAM MapReduce application resource management by completing the steps in this topic, and also disabling 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 REST service:
    egosh service stop REST
  2. Copy server_rest.xml.nonssl to server_rest.xml:
    • Windows: %EGO_CONFDIR%
    • Linux®: $EGO_CONFDIR
    Important: Check for port conflicts in server_rest.xml. Ensure especially that the HTTP port is free and not used by any other service. The HTTP port (specified in the httpPort attribute) is by default 8180 for REST.
  3. Start the REST service:
    egosh service start REST
    The RESTful APIs are now accessible over HTTP.
    • To access the APIs for EGO resource management, enter (for example) http://restserver.example.com:8180/platform/rest/ego/v1.
    • To access the APIs for EGO package deployment, enter (for example) http://restserver.example.com:8180/platform/rest/deployment/v1.
    • To access the APIs for SOAM MapReduce application resource management, enter (for example) http://restserver.example.com:8180/platform/rest/sym/v1.

What to do next

To fully disable security, also disable security for the cluster management console.