Microsoft Sharepoint Products and Technologies Resource Kit eBook

684 Part VIII: Securing SharePoint Products and Technologies
Configuring SSL Bridging on the Web Publishing Rule
The default configuration for SSL bridging is to forward external HTTPS requests as
HTTPS requests to the internal website. This configuration provides an end-to-end
secure connection between the external client and the portal site. If this is the configuration
that you require, you do not need to perform any additional configuration
steps.
However, it is possible to configure the Web publishing rule to bridge incoming
HTTPS connections to the ISA Server as HTTP connections from ISA Server to
the internal portal site. In this case, the internal portal site should not be configured
to request SSL connections. If this is your preferred configuration, do the following:
1. Open the ISA Management console, click Servers and Arrays, click your
server name, and then click Publishing. Click Web Publishing Rules, rightclick
the rule you would like to configure, and select Properties.
2. In the Properties dialog box, click Bridging tab.
3. On the Bridging tab, select Redirect SSL requests as: HTTP requests (terminate
the secure channel at the proxy).
4. Click Require secure channel (SSL) for the published site. Depending on
your company security policy, you might need to select Require 128-bit
encryption.
5. Click Apply, and then click OK.
When you configure the SSL-to-HTTP bridging for a SharePoint Portal Server
extranet site, you might encounter two issues with accessing the search results links
from an external client, as follows:
■ Because the portal site is not SSL-enabled, the links’ URLs in the search results
page are generated with HTTP protocol, not HTTPS protocol. Therefore, when
a user clicks any of them, the HTTP request will be sent back to the portal site.
However, the Web publishing rule as configured requires an HTTPS connection
for the portal site, so the HTTP connection request will fail.
■ The links’ URLs in search results use the internal name of the portal site, which
cannot be resolved to an IP address by the external client. In addition, the destination
set in the Web publishing rule uses an external FQDN, which is different
from the internal name.
Both of these issues can be addressed by configuring the link translation on the
ISA Server. The second issue—broken links because of using internal names—can
also be addressed by configuring alternate portal site access settings on the portal
site. We will look into configuring link translation in the next section. Configuring
alternate portal access settings is discussed in detail in Chapter 13, “Installing and
Configuring Windows SharePoint Services in an Extranet.”