FP: How to Use Secure Sockets Layer to Secure Pages in Your Web

Last reviewed: March 18, 1998
Article ID: Q174424
The information in this article applies to:
  • Microsoft FrontPage 98 for Windows
  • Microsoft FrontPage 97 for Windows with Bonus Pack

SUMMARY

When you create a new FrontPage Web, you can select the Secure Connection Required option. When you select this option, the entire Web will use the Secure Socket Layer (SSL) port to encrypt all data sent to or from FrontPage. This is called secure authoring. You can also specify whether you want to use the SSL port for links to specific pages within a normal, unsecured Web. This is called secure browsing. This article describes how to accomplish both secure authoring and secure browsing.

MORE INFORMATION

Secure Authoring

To use SSL for secure authoring, follow these steps:

  1. On the File menu, point to New, and then click FrontPage Web.

  2. In the New FrontPage Web dialog box, click Change.

  3. In the Change Location dialog box, type the name of the new FrontPage Web and click to select the "Secure connection required (SSL)" check box.

  4. Click OK.

  5. Click OK again.

SSL provides a highly secure (encrypted and authenticated) communication between the client and the server, based on public-key cryptography. To send a secure message, the sender encrypts the message with the recipient's public key, and the recipient decrypts the message with the recipient's private key. Since only the recipient has the private key that can decrypt the message, the message is secure.

To guarantee authenticity, a certificate accompanies the public key. A certificate is a digital signature on a digest of the friendly (human readable) name of the participant, together with the participant's public key. The certificate is encrypted with the private key of the certifying authority. To check the authenticity of the public key of the participant, anyone may compute the digest of the friendly name and public key for that participant, then decrypt the certificate for that public key using the public key of the certifying authority, and check that the same digest results.

For additional information about the use of security certificates with FrontPage, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q171675
   TITLE     : FP97: Socket Code 13101 Error Opening, Creating New Web

Secure Browsing

If you want to require that SSL be used to browse some of your pages you can mix ports on a single Web by using a fully qualified Uniform Resource Locator (URL), such as http://example.microsoft.com/default.htm.

Web servers use a separate port for SSL connections. Instead of linking to default.htm, link to https://example.microsoft.com/default.htm go from the default port (usually 80) to the SSL port. To go from the SSL port to port 80, link to http://example.microsoft.com/default.htm.

To create a SSL link from a page in your Web for secure browsing, follow these steps:

  1. In FrontPage Editor, select the text you want to use for your hyperlink.

  2. On the Edit menu, click Hyperlink.

  3. In the URL box change http:// to https:// and type the complete URL of your page. For example, type the following:

          https://example.microsoft.com/default.htm
    

  4. Click OK.

For additional information about security features and Microsoft Internet Information Server (IIS), please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q142868
   TITLE     : IIS: Authentication & Security Features


Additional query words:
Keywords : fpext kbinterop kbnetwork kbdta
Version : WINDOWS:97,98
Platform : WINDOWS
Hardware : x86
Issue type : kbhowto


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 18, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.