Introduction to configuring FMS for HTTPS

HTTPS creates a secure channel over an insecure network. HTTPS protection is based on a major certificate authority guaranteeing that your web server is the entity it claims. This protection method uses verified and trusted server certificates, private keys (your keystore), and public keys (the certificate signing request). Selecting HTTPS during Teamcenter installation If you are using Deployment Center for your Teamcenter installation, on the Components tab, ensure the HTTPS Config component is configured. (Distributed environments have multiple HTTPS Config components.) FMS uses this HTTPS configuration. If you are using TEM to install Teamcenter, select HTTPS as your protocol during installation.,You are prompted to supply the appropriate proxy, host, and port information. You are also asked whether you want to add the URL of the local host to the list of servers defined in the Fms_BootStrap_Urls preference. Your only postinstallation tasks are to: Use a trusted certificate to generate a keystore and key entry. Trusted certificates are purchased from third-party certificate vendors, such as VeriSign or Thawte. Using untrusted (self-signed) certificates requires additional configuration to either import the certificate into the client certificate keystores, or to modify FMS properties to permit clients to connect to servers using self-signed certificates. Siemens Digital Industries Software does not recommend using self-signed certificates. Generate a certificate signing request. (If you upgrade from a previous version of Teamcenter, you must transfer all the HTTPS certificate information to the upgraded Teamcenter installation.) Switching to HTTPS after selecting HTTP during Teamcenter installation If you selected HTTP as your protocol during Teamcenter installation, but sometime after installation decide to configure FMS to use HTTPS, perform the following tasks: Use a trusted certificate to generate a keystore and key entry. Generate a certificate signing request (CSR). Modify the FMS primary configuration file to reflect the new HTTPS addresses. Add the URL of the local HTTPS host to the list of servers defined in the Fms_BootStrap_Urls preference. Update any installed FCCs.