Set up SSL for your TeamForge site on Red Hat

To force all TeamForge traffic to use SSL encryption (HTTPS), state that preference in your configuration file.

1. Open the site-options.conf file, the master configuration file that controls your TeamForge site.
   • vi /opt/collabnet/teamforge-installer/8.2.0.0/conf/site-options.conf
   Note: vi is an example. Any *nix text editor will work.
2. Set the options to enable SSL for the site.
   1. Set the SSL variable to on.
   2. 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
   3. 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.
3. In the site-options.conf file, make sure the value of the DOMAIN_localhost variable matches that of your SSL certificate.
4. Rename the /etc/httpd/conf.d/ssl.conf file to /etc/httpd/conf.d/ssl.conf.old, if it exists.
5. Stop TeamForge.
   • /etc/init.d/httpd stop
   • /etc/init.d/collabnet stop
6. Run the installer.
   • cd /opt/collabnet/teamforge-installer/8.2.0.0
   • ./install.sh -r -I -V
7. 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.

8. Rename the /etc/httpd/conf/httpd.conf.cn_new file to httpd.conf, if it exists.
9. Start TeamForge.
   • /etc/init.d/httpd start
   • /etc/init.d/postgresql-9.3 start
   • /etc/init.d/collabnet start