Iis – ISA Server 2006 web publish issue

It can be done with the regular "Publish Web sites" wizard. If the external website is https://mysvn.com then ISA will need to have a certificate installed for https://mysvn.com; this is configured the listener. (For ease of use I have a wildcard certificate for https://*.mycompany.com and a lisetener called "generic https listener" so I don't need a seperate listener for each site)

If external clients use https to contact ISA then it is best if the ISA uses https (and the same domain name) to contact the webs server - this eliminates problems where a web server returns an internal link (http://internalname.local) that makes it back to the client instead of being re-written by ISA. The SSL certificate on the web server should be trusted by the ISA server, either because it's from a trust root server (i.e.: a proper paid for certificate) or you've set up your own certificate issuing system.

Authentication delegation should be set to "no delegation, but client can authenticate directly" otherwise ISA will try to take over user authentication.

You should be able to do that using different subfolders in your web publishing rules.

This Microsoft TechNet article explains the details and has some walk-throughs for ISA Server 2004:

Web publishing provides you detailed control over access to content. Web publishing rules are rich in features, including the following:

• Mapping requests to specific internal paths. You can limit the portions of your servers that can be accessed.
• Restricting access to specific users, computers, or networks. You can restrict access, to further improve security.
• Requiring user authentication. User authentication can be passed through to the Web server, eliminating the need to reauthenticate at the Web server.
• Providing link translation. You can handle links to internal servers.
• Providing SSL bridging. You can encrypt traffic between the ISA Server computer and the Web server.

Search for this section:

Publishing Web server folders on the Internal or perimeter network to one domain name

You can publish specific folders on a Web server on the Internal network or on a perimeter network. In this scenario, both folders are published to the same domain. For example, you want to publish the \news folder to www.fabrikam.com/news, and the \updates folder to www.fabrikam.com/updates.

For ISA Server 2006 there is this article (or as Word file here), which explains the options you have for publishing. Search for "Web Publishing Rule Properties" and "Path Mapping" inside the document.