> #### Using advanced HTTP and HTTPS options with the Fathom Management Web server

> You can use the following advanced options when configuring Fathom to use HTTP or HTTPS:

> - Use a Trust Keystore other than the demo provided by Fathom.
> - Identify trusted clients for HTTP and/or HTTPS.

> To use the advanced options:

> 1. From the Fathom Web Server Configuration page, click Advanced Options. The expanded Fathom Web Server Configuration page appears:

> 2. Under HTTP Configuration, type the name of one or more trusted clients in the Trusted clients field. If you type more than one trusted client, use a comma-delimited list.
> You can identify trusted clients by machine name, subnet, or IP address.

> Under HTTPS Configuration, notice that the following fields are prefilled with data taken from the demo keystore, which is `demoWebServerIdentityKeystore.jks`:

> - Keystore path name
> - Keystore pass phrase
> - Alias
> - Alias pass phrase
> The Keystore pass phrase, alias, and alias pass phrase are all case-sensitive.

> Notice also the following details related to the demo certificate information provided by Fathom:

> - Owner — The Common (CN) and Organization (O) name components of the Distinguished Name (DN), whose public key the certificate identifies. For the demo, the owner is Demo or localhost, Progress Software Corp.
> Note that most popular browsers expect the common name portion of the owner name to be the DNS host name of the machine that is using the certificate for SSL. If a certificate has a different common name, as does the Fathom demo certificate, the browser notifies you of the difference when you connect to a Web server using this certificate.

> - Issuer — The Common (CN) and Organization name components of the Distinguished Name (DN), the organization that signed the certificate.
> - Type — The type of certificate. X.509 is the most widely accepted format and is currently the only format supported by the JDK keytool. This is also the default format used by SSL.
> - Public key — The algorithm used to generate the public/private key pair. This should always be RSA, which is the only algorithm that Netscape and Internet Explorer browsers recognize.
> - Signature algorithm — The algorithm used by the CA to sign the certificate.
> - Version — The version of the X.509 standard that applies to this certificate. There are currently three certificate versions: V1, V2, and V3.
> - Valid from — The dates for which the certificate is valid.
> 3. Type the name of one or more trusted clients in the Trusted clients field. If you type more than one trusted client, use a comma-delimited list.
> 4. Click Submit. A message appears confirming that the configuration has been successfully updated.
> 5. Click OK.

> Note that changes you make to the configuration might require you to reconnect (log in again) to Fathom.

Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095