Your suggested change has been received. Thank you.


Suggest A Change….


CTE Administration

Load Balancer


Please Note:

Load Balancer

This document describes the configuration steps to allow CTE agents communicate with a CipherTrust Manager cluster behind a network load balancer.


Make sure the load balancer is configured with the nodes of the CipherTrust Manager cluster. Refer to Clusters and Nodes for details on creating a CipherTrust Manager cluster.

Configure the Load Balancer on CipherTrust Manager

After completing the prerequisites, you can configure the load balancer. Click the desired tab to view the instructions.

  1. On the load balancer, log on to the CipherTrust Manager GUI.

  2. Click Admin Settings > Properties.

  3. Under LOAD BALANCER ADDRESS, in the Value, specify the hostname or IP address of the load balancer.

  1. Acquire an authorization token.

  2. Go to the Properties section.

  3. Update the name of the load balancer address.

    Run the API

    patch /v1/configs/properties/{name}



    Sample Output

        "name": "LOAD_BALANCER_ADDRESS" ,
        "value": "",
        "description": "Add IP/URL/Hostname of load balancer configured with CM. Default value is empty for CM."


  • If the nodes are configured with the load balancer, the configured Server Settings for the CTE Profiles on the CipherTrust Manager will not be applicable.

    Refer to Configuring Server Settings for details.

  • The Agent Information on the CipherTrust Manager will be unavailable for the CTE clients registered with the load balancer.

  • If the load balancer configuration is deactivated and the CipherTrust Manager cluster is also removed, the agents registered with the load balancer need to be reregistered with the desired CipherTrust manager.

  • When the load balancing setup changes to the non-load balancing mode, that is, when the load balancing configuration is removed, any configuration changes take time to reflect on the registered clients. If a client is down/unavailable, the configuration changes would not be updated for that client.

    Workaround: To update the client with the configuration changes, reregister the client after it is up and running!