Secure Communications

Use this dialog box to configure Secure Sockets Layer (SSL) encrypted communication for visitors using a Web browser that supports secure communications (URLs starting with https:// ).

Before you can use your Web server’s SSL security features, you must obtain a valid server certificate from a trusted, third-party organization, called certificate authority. This cannot be done in the Internet Services Manager (HTML); you must use the IIS snap-in.

Require a secure channel (SSL)To require an encrypted communication link for a Web browser to connect with this Web site, directory, or file, select this option.

Require 128 bit encryptionTo require a 128-bit encrypted communication link for a Web browser to connect with this Web site, directory, or file, select this option.

Important   Due to export restrictions, the 128-bit key strength encryption feature is available only in the United States and Canada.

Client certificates

You can configure your Web server to either accept, require, or reject client certificates as a means of establishing a connection with a particular file or directory. A client certificate is a digital identification issued by a trusted, third-party organization, called a certification authority.

Do not accept client certificatesTo allow users access without being prompted to present a client certificate, select this option.

Accept client certificates To allow users with client certificates access, but not require the certificate, select this option. Users with client certificates can be used in mappings; users without them will use other authentication methods.

Require client certificates To allow only users with a valid client certificate to connect, select this option. Users without a valid client certificate will be denied access. The Require secure channel (SSL) check box must be selected to use this option.

Enable client certificate mapping

To authenticate users who log on with a valid client certificate, select this option. Mappings match information contained in a client's certificate against Windows user account information.


© 1997-1999 Microsoft Corporation. All rights reserved.