Connecting Through a Proxy Server

Certain core components and features, including the Recommender, Mobile, and Apps Market services, require Jive to access information from across the firewall. If you use a proxy server to access the Internet, setting up the proxy connection using the Proxy Server settings in the Admin Console ensures you can connect to Mobile and the Apps Market. You can also set exceptions if you want to connect to certain hosts directly, rather than through the proxy server.
Fastpath: Admin Console: System > Settings > Proxy Server

See Advanced Proxy Configurations below for some situations that may require additional workarounds.

Setting JVM Properties for Recommender

Connecting to the Recommender service requires setting JVM properties as well after you complete the Activity Engine installation. To set them:

  1. Modify start in /usr/local/jive/services/eae-service/bin/ to add the following java args to the service invocation: -Dhttp.proxyHost=webproxy_address -Dhttp.proxyPort=webproxy_port -Dhttp.proxyUser=webproxy_user -Dhttp.proxyPassword=webproxy_pwd. For example, add:
    -Dhttp.proxyHost=webproxy.eng.jiveland.com -Dhttp.proxyPort=3128 -Dhttp.proxyUser=jive -Dhttp.proxyPassword=jive 
    The proxyUser and proxyPassword properties are required. If your proxy server does not require a user name and password, include these options with blank values.
  2. If the system is NOT the production instance go to System > Management > System Properties and set the system property jive.eae.instance.type to the value 2.
  3. Restart the Activity Engine instance and the application servers.

Advanced Proxy Configurations

If you have DNS proxying enabled, you also need to set the jive.apps.proxy.whitelist.cidrs system property to include the IP address (single node) or CIDR addresses of your proxy server. Domain names are not supported. You can separate multiple addresses with spaces.

If your site uses client certificate validation, you should contact Support for assistance.

Reverse proxying can modify data in ways that are not compatible with running Jive. Reverse proxies are often configured to reject GETs with special characters in the query string, strip the bodies from PUT commands, and add prefixes to cookie names. For example, Jive Apps require the colon (:) character to be supported in URLs. If you use IIS-based reverse proxying with .NET 4.5 or earlier, colons are blocked by default. In this case, upgrading to .NET 5.0 resolves the problem.