You can configure an HTTPS connection between the external client and the ISA Server. This connection ends on the ISA Server computer. You can decide that traffic should be passed from the ISA Server computer and from the internal Web server over HTTPS to preserve the encrypted channel. Or, you can forward traffic to the internal Web server over HTTP.
In an HTTPS-to-HTTPS connection, ISA Server requires a server certificate to authenticate to external clients. Additionally, the internal Web server requires a server certificate to authenticate to the ISA Server computer.
In an HTTPS-to-HTTP scenario, a server certificate is required only on the ISA Server computer. Optionally, you can also configure client certificates for client authentication. You cannot request a server certificate directly on the ISA Server computer. Typically, you request and install a certificate on the internal Web server and then export the certificate to the ISA Server computer.
For more information about how to configure and troubleshoot Web publishing on an ISA Server computer, visit the following Microsoft Web site:
For more information about how to configure Web publishing for different scenarios in ISA Server, Enterprise Edition, visit the following Microsoft Web site:
For more information about how to configure Web publishing for different scenarios in ISA Server, Standard Edition, visit the following Microsoft Web site:
For more information about digital certificates, visit the following Microsoft Web site:
For more information about how to troubleshoot SSL certificates in ISA Server, visit the following Microsoft Web site: