You are here: FME Server Administrator's Guide > Securing FME Server > Configuring for HTTPS

Configuring for HTTPS

HTTPS ensures that communication between the client and server is encrypted, so that if it is intercepted, the third party cannot easily view or use the information. For FME Server, you can use HTTPS to ensure that sensitive log in information is not exposed. This is especially important if you are using the Active Directory integration.

Enabling FME Server SSL Support

To enable SSL support:

  1. Modify service URLs to use HTTPS instead of HTTP.
  2. Enable SSL on the web and/or application server.

Modifying Service URLs to Use HTTPS

To enable SSL for a service, open the FME Server Web User Interface, click Services, and click the desired service in the table.

The Editing Service page opens.

In the URL field, change HTTP to HTTPS, and modify the port number, if required. Typically SSL is configured on either port 8443 or 443.

Enable SSL on the Web and/or Application Server

Depending on the method, instructions to set up SSL on different application servers vary. The following example provides steps for setting up SSL for Apache Tomcat 7, using self-signed certificates.

For development and testing purposes, self-signed certificates are supported. For production use, we recommend that you use SSL certificates from a verified SSL certificate authority.

For any HTTPS (SSL) page, a certificate is required. First, you must generate a keystore that contains a certificate chain using the keytool command from the Java Developer Kit (JDK).

To set up SSL for Apache Tomcat 7 using self-signed certificates, follow these steps:

  1. Open the command prompt.
  2. Type the following command:

    keytool -genkey -alias tomcat -keyalg RSA

    If your path is not set to the Java bin directory, navigate to that directory and type the appropriate command.

    Note:  A JDK must be installed to use the keytool command.

    A message prompts you to enter a keystore password.

  3. Enter changeit.

    You can give the keystore password a different name; however, if you do, you must make some changes later.

  4. Enter the required details, shown here:

    A message prompts you to enter the alias password, which must be the same as the keystore password.

  5. Enter the same password you entered in step 3.

    A keystore is generated in the following location:

    <drive>:\Users\<username>\.keystore

    where <drive> is C: and <username> is hnguyen.

  6. Copy the .keystore file to the Tomcat directory, and then copy the path to the file.

    If you are using the default web application included with FME Server, Tomcat is located at:

    <FME Server Install DIR>\Utilities\tomcat

  7. Open the server.xml file:

    <TomcatDir>\conf\server.xml

  8. Locate the Connector code block, and replace it with the following:

    <Connector protocol="org.apache.coyote.http11.Http11Protocol"

    port="443" minSpareThreads="5"

    enableLookups="true" disableUploadTimeout="true"

    acceptCount="100" maxThreads="200"

    scheme="https" secure="true" SSLEnabled="true"

    keystoreFile="C:\Program Files\Apache Software Foundation\Tomcat 6.0 2010

    beta\conf\.keystore"

    keystorePass="changeit"

    clientAuth="false" sslProtocol="TLS" />

  9. Be sure to set the keystoreFile path to the correct location and the keystorePass to the password you entered in step 3.
  10. In the Apache Tomcat's server.xml file change the Listener className line (found at the beginning of the file) to how it's written below:

    <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine=‘off'/>

  11. Your configuration is complete so save the server.xml file.
  12. Restart your Tomcat application.
  13. If you are using the default FME Server Application Server, restart that service.
  14. Open a browser and navigate to https://localhost.

    This should show you the same Tomcat home page, but in a secured format.

  15. Note:  If you use port 443 in your Tomcat server.xml file, you're able to omit the port number in your URL links; that is, you only need to type https://localhost.

Safe Software Inc. www.safe.com