Configuring SSL Termination on Load Balancers

Overview

This article shares the process of configuring Secure Sockets Layer (SSL) termination on your load balancer. This is required to secure a Jive installation. Additionally, running a Jive site behind a load balancer enables you to use the Jive web-application nodes on a separate, non-public network.

Environment

On-Premise Jive

Requirement

Jive community manager admin access

Process

Follow these general guidelines (with the help of your IT team) to configure SSL termination on your load balancer:

1. Configure your load balancer pool to use the SSL certificates acquired for the Jive sites.
   
   
2. Create a DNS record for each domain that resolves to the load balancer pool's IP address.
   
   
3. Add all web-application node addresses and ports for each site to the balancer pool. For example, add:
   • http://myapp-wa01.internal.mycompany.com:8080
   • http://myapp-wa02.internal.mycompany.com:8080
   • http://myapp-wa03.internal.mycompany.com:8080
     
     
4. On each web-application node, set the required proxy-related properties, and restart. For example:
   • jive set webapp.http_proxy_name community.mycompany.com
   • jive set webapp.http_proxy_port 443
   • jive set webapp.http_proxy_scheme https
     
     
5. Make sure that thejiveURL property in Jive's core database is set to the address of the load balancer by going to System > Management > System Properties.
   
   
6. Double-check the settings of the jiveURL property.

   Note: An incorrect parameter value can prevent your Jive site from working correctly after restarting.

7. Restart Jive on all web-application nodes.