Protocol configuration after a server upgrade

When you upgrade by using the server installer program and select to keep existing properties, you must configure properties after installation if you change your protocol selection.

Note: From V9.1.3, HTTPS is enabled by default. If you do not keep existing properties during the upgrade and you clear the Force targets to use HTTPS option, you must configure properties after installation. For more information, see Enabling HTTP access.

Changing from HTTPS to HTTP

Your previous server installation is configured to use HTTPS and you clear Force targets to use HTTPS during the upgrade. To access and log on to the server UI by using HTTP, you must also complete the following steps after the upgrade.

  1. Edit the trc.properties file and set enforce.secure.alllogon to false.
  2. Edit the following file, where [INSTALLDIR] is the BigFix® Remote Control server installation directory.
    Windows systems
    [INSTALLDIR]\wlp\usr\server\trcserver\cookie.xml
    Linux systems
    [INSTALLDIR]/wlp/usr/server/trcserver/cookie.xml
  3. Set <httpSession cookieSecure="false"/> and save the file.
  4. Restart the server service.

Changing from HTTP to HTTPS

Your previous server installation is configured to use HTTP and you select the Force targets to use HTTPS option during the upgrade. To access and log on to the server UI by using HTTPS, you must also complete the following steps after the upgrade.

  1. Edit the trc.properties file and set enforce.secure.web.access, enforce.secure.weblogon, and enforce.secure.alllogon to true.
  2. Edit the following file, where [INSTALLDIR] is the BigFix® Remote Control server installation directory.
    Windows systems
    [INSTALLDIR]\wlp\usr\server\trcserver\cookie.xml
    Linux systems
    [INSTALLDIR]/wlp/usr/server/trcserver/cookie.xml
  3. Set <httpSession cookieSecure="true"/> and save the file.
  4. Restart the server service.