iTP Secure WebServer System Administrators Guide (Version 7.5+)

• Whether the server checks for TLS, SSL, or both

• Whether the server requests or requires client authentication (or neither)

For complete information about these options, See “AcceptSecureTransport” (page 200).

NOTE: The server checks for connections on the ports specified by both the Accept and the

AcceptSecureTransport directives.

4. Use the RequireSecureTransport commands in the Region directive to control how clients access

the server and its contents as described in “Controlling Access and Privacy” (page 74).

5. Restart the server.

6. Include security properties in HTML documents.

Use the HTTPS protocol specifier (https) in anchor specifications for the Web client use to TLS or

SSL, as this example shows:

https://www.oregon-club.com/recipes

If you are using a TLS or SSL port other than the default (443), specify the port:

https://www.oregon-club.com:444/recipes

Managing Certificates

Each iTP Secure WebServer must have a private/public key pair for encrypting and decrypting

secure transactions. The public key must be signed by a CA in the form of a certificate. The certificate

verifies the binding of the public key to a particular DN, which uniquely identifies a particular

Web server. (See “Requesting a Certificate” (page 59).)

The same certificate can be used for both TLS and SSL.

This section describes how to manage certificates and covers these topics:

• “Formatting Distinguished Names (DNs)” (page 55)

• “Using the Keyadmin Utility to Manage Keys and Certificates” (page 56)

• “Using Server Certificate Chains With the iTP Secure WebServer” (page 72)

Formatting Distinguished Names (DNs)

DNs are specifications that identify persons or organizations to associate with particular keys.

DNs consist of lists of attributes that identify such entities as company name and company location.

For example:

• CN="Compedia, Inc."

• ST=New Hampshire

CAs use DNs to formally bind particular persons or organizations to particular keys. The individual

attributes in DNs are separated by commas and must be specified in the order required by a

particular CA.

Table 1 (page 55) lists and describes the most common DN attributes. For complete list of supported

DN attributes, See Table 4 (page 68).

Table 1 Common Distinguished Name (DN) Attributes

DescriptionAttribute

Common Name: The name of the owner of the certificate.CN

Organizational Unit: The name of the owner's organizational subdivision. DNs can include multiple

OUs. An example of multiple OUs is shown after this table.

Organization: The name of the owner's organization (company name).O

Managing Certificates 55