Set up SSL for your TeamForge site

SSL encryption (HTTPS) is enabled by default in TeamForge 17.1 and later.

1. Back up your existing /etc/httpd/conf/httpd.conf file.
2. Open the site-options.conf file, the master configuration file that controls your TeamForge site.
   • vi /opt/collabnet/teamforge/etc/site-options.conf
   Note: vi is an example. Any *nix text editor will work.
3. Set the options to enable SSL for the site.
   1. Set the SSL_CERT_FILE variable to the location of the file that contains your site's SSL certificates.
      • SSL_CERT_FILE=www.example.com.crt
   2. Set the SSL_KEY_FILE variable to the location of the file that contains your site's RSA private keys.
      • SSL_KEY_FILE=www.example.com.key
      Important: Select a location for your cert file and your key file that is permanent across restarts. Don't use a temp directory that can be wiped out.
4. In the site-options.conf file, make sure the value of the <hostname>:PUBLIC_FQDN token matches that of your SSL certificate.
5. Rename the ssl.conf file (RHEL/CentOS: /etc/httpd/conf.d/ssl.conf) as ssl.conf.old, if it exists.
6. If you are converting an existing site to use SSL (that is, if your site already has had users accessing it via HTTP and not HTTPS), you must update your site's publishing repository to use the new SSL settings.

   To do this, ask your CollabNet support representative for the fix-publishing-repos-to-ssl.py script.

7. Stop TeamForge.
   • /opt/collabnet/teamforge/bin/teamforge stop
8. Deploy services.
   • /opt/collabnet/teamforge/bin/teamforge provision
   Note:

   The "provision" command prompts for response before it bootstraps or migrates data during TeamForge installation and upgrade respectively. Enter "y" or "N" to proceed. For more information, see the TeamForge script.

   TeamForge 17.4 (and later) installer expects the system locale to be LANG=en_US.UTF-8. TeamForge "provision" command fails otherwise.