This section describes how to configure a SharePoint Portal Server deployment with a single portal site on a single virtual server, exposed to both the corporate intranet and to the extranet using only Basic authentication and SSL.
In this scenario, the portal site is hosted on the Default Web Site in IIS (that is, on the virtual server for the Default Web Site).
Before performing the steps that follow, ensure that the following are true:
- SharePoint Portal Server is installed.
- There is one portal site hosted on the Default Web Site in IIS.
- You can access the portal site from the corporate intranet.
To enable the scenario described in this section, you must do the following steps, each of which is explained in detail later in this section:
- Configure Basic authentication on the Default Web Site in IIS.
- Install an SSL server certificate on the Default Web Site in IIS.
- Verify that you can access the portal site by using an internal SSL fully qualified domain name (FQDN) URL.
- Configure IIS to require SSL for the Default Web Site.
- Modify the default URL for the portal site.
- Verify that the proxy server settings for SharePoint Portal Server search are correctly specified.
- Configure the SharePoint Portal Server search service to use Basic authentication when crawling content sources.
- Create a public DNS entry.
- Configure the network adapters in the external ISA Server 2000 computer.
- Configure ISA Server 2000 to not intercept HTTP requests that use the OPTIONS verb.
- Ensure that the appropriate SSL server certificates are installed on the external ISA Server 2000 computer.
- Configure the external ISA Server 2000 computer to allow outbound connections to the Internet.
- Edit the web.config file.
- Configure the external ISA Server 2000 computer to listen for incoming requests on the appropriate IP address.
- Create a destination set on the external ISA Server 2000 computer.
- Create a Web publishing rule on the external ISA Server 2000 computer.
- Verify that the Web publishing rule properties are correct.
- Configure an alternate access setting that uses the public (external) FQDN URL that users will use to access the portal site.
- Verify that you can access the portal site through the Internet.
The following sections include procedures for the major steps above.
The examples in the following table are used in the procedures for this scenario.
| Element |
Example used in this scenario |
| Extranet domain name |
Perimeter.Net |
| Intranet domain name |
Corp.Net |
| Front-end Web server internal FQDN |
ServerName.Perimeter.Net, where ServerName is the NetBIOS computer name of the front-end Web server |
| Front-end Web server internal FQDN URL (HTTP) |
http://ServerName.Perimeter.Net, where ServerName is the NetBIOS computer name of the front-end Web server |
| Front-end Web server internal FQDN URL (SSL) |
https://ServerName.Perimeter.Net, where ServerName is the NetBIOS computer name of the front-end Web server |
| Load-balancing internal FQDN |
Portal.Perimeter.Net (resolves to the load-balancing virtual IP address) |
| Load-balancing internal FQDN URL (HTTP) |
http://Portal.Perimeter.Net |
| Load-balancing internal FQDN URL (SSL) |
https://Portal.Perimeter.Net |
| External FQDN |
ExtranetPortal.Perimeter.Net (resolves to an IP address on the external network adapter on the external ISA Server 2000 computer) |
| External FQDN URL |
https://ExtranetPortal.Perimeter.Net |
| Default Web Site in IIS |
Hosts existing portal site, TCP port 80, SSL port 443 |
