Disable a Load Balancer and Virtual HostDisable a Load Balancer and Virtual Host
To stop using a load balancer and virtual host, for example, when you remove the web tier deployment, you disable them from the Operations Console. After disabling a load balancer and virtual host, you must perform additional steps to keep risk-based authentication (RBA), self-service, and dynamic seed provisioning functioning. See “After you finish.”
Before you begin
You must be a Super Admin.
Procedure
-
In the Operations Console on the primary instance, click Deployment Configuration > Virtual Host & Load Balancing.
-
If prompted, enter the Super Admin User ID and password.
-
On the Virtual Host & Load Balancing page, deselect Configure a virtual host and load balancers.
-
Click Save.
-
On the confirmation page, read Mandatory Next Steps.
-
Click Done.
After you finish
In the Operations Console, perform the appropriate mandatory next steps.
-
Configure the virtual hostname to resolve to the public IP address of the web tier.
-
To redirect authentication requests to the primary instance, generate a new integration script for each web-based application using RBA, and then redeploy the integration scripts.
-
If the deployment uses dynamic seed provisioning, update the hostname for the CT-KIP URL with the hostname of the primary instance. Update the port to 7004. In the Security Console, go to Setup > System Settings. Click Tokens.
-
If the deployment uses the Self-Service Console, update the Self-Service Console URL with the hostname of the primary instance. Update the port to 7004. In the Security Console, go to Setup > Self-Service Settings. Click E-Mail Notifications for User Account Changes.
Related Concepts