Your suggested change has been received. Thank you.

close
Thales Logo

All

  • All
  • CipherTrust Manager
  • CipherTrust Application Data Protection (CADP)
  • CipherTrust Application Key Management (CAKM)
  • CipherTrust Batch Data Transformation (BDT)
  • CipherTrust Cloud Key Management (CCKM)
  • CipherTrust Data Discovery and Classification (DDC)
  • CipherTrust Data Protection Gateway (DPG)
  • CipherTrust Database Protection (CDP)
  • CipherTrust Intelligent Protection (CIP)
  • CipherTrust Integrations
  • CipherTrust Migrations
  • CipherTrust RESTful Data Protection (CRDP)
  • CipherTrust Transparent Encryption (CTE)
  • CipherTrust Transparent Encryption Userspace (CTE-U)
  • CipherTrust Secrets Management (CSM)
  • CipherTrust Vaulted Tokenization (CT-V)
  • CipherTrust Vaultless Tokenization (CT-VL)
  • CTE-Linux
  • CTE-Windows
  • CTE-AIX
  • CTE-K8s
  • CTE-U
  • Crypto Command Center
  • Data Protection on Demand
  • Luna Cloud HSM
  • Luna Network HSM
  • Luna PCIe HSM
  • Luna USB HSM
  • OneWelcome Identity Platform
  • ProtectApp LUKS
  • ProtectServer 2 HSM
  • ProtectServer 3 HSM
  • SafeNet Trusted Access (STA)
  • SafeNet MobilePASS+
  • SafeNet MobilePASS+ for Android
  • SafeNet MobilePASS+ for Chrome
  • SafeNet MobilePASS+ for macOS
  • SafeNet MobilePASS+ for iOS
  • SafeNet MobilePASS+ for WatchOS
  • SafeNet MobilePASS+ for Windows
  • SafeNet Synchronization Agent
  • SafeNet Logging Agent
  • SafeNet Agent for FreeRADIUS
  • SafeNet Agent for NPS
  • SafeNet Agent for Windows Logon
  • SafeNet Authentication Service Private Cloud Edition (SAS PCE)
  • SafeNet Remote Logging Agent
  • SafeNet Keycloak Agent
  • SafeNet IDPrime Virtual (IDPV)
  • SafeNet FIDO Key Manager
  • SafeNet FIDO Key Manager for Android
  • SafeNet FIDO Key Manager for iOS
  • SafeNet FIDO Key Manager for Windows
back

CTE Administration

Load Balancer

search

Please Note:

printsuggest an editpdf paneldownload

Load Balancer

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

copy link to clipboardPrerequisites

Make sure a passthrough network 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.

Note

Only network load balancers with passthrough authentication are supported.

copy link to clipboardConfigure 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. Login to the root domain as an Application Administrator.

  2. Navigate to Admin Settings > Properties.

  3. In Load Balancer Address, add an IP address or hostname for the load balancer to the Value field.

  4. Click Update to update it.

  1. Authenticate to the REST API.

  2. Go to the Properties section.

  3. Update the name of the load balancer address.

    Run the API

    patch /v1/configs/properties/{name}

    Example

    /v1/configs/properties/LOAD_BALANCER_ADDRESS

    Sample Output

    {
    "name": "LOAD_BALANCER_ADDRESS" ,
    "value": "cte-cm-d91617b26a55d596.elb.us-east-1.amazonaws.com",
    "description": "Add IP/URL/Hostname of load balancer configured with CM. Default value is empty for CM."
}

copy link to clipboardLimitations

  • 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!

On this page