Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Sharepoint + SSL + ISA server = Headache!!!

Status
Not open for further replies.

DKMr

IS-IT--Management
Oct 7, 2003
18
US
Hello, I have some issues with SSL and Sharepoint.

I have a Sharepoint Team Services site published and working through an ISA 2000 server. I have recently installed a SSL certificate on my web server and them exported it, and then imported and installed it on my ISA server.

From with in my network, on the LAN, I can go to the Sharepoint Site with HTTP or HTTPS and it works fine. All the links to various sites and document libraries work.

When I access the Sharepoint site over the internet with HTTPS I can get to the main team sites but some of the links on the page do not redirect as HTTPS, but instead they redirect as HTTP and therefore fail. WHY?

My web publishing Bridging tab settings are set as so:

Redirect HTTP Requests as Http Requests. Redirect SSL Requests as HTTP (terminate secure channel at the proxy)

If I set the setting on my Action tab to not "Send the original host header to the publishing server instead of the actual one (specified above)", I get promted twice to authenticate and the links that redirect to HTTP work, but of course they are not secure.

What is going on? Please help!

Thanks,

DKM
 
Well, I solved my own problem and I'll put my solution here to help anyone else who has the same problem.

I configured the ISA server redirect the traffic as SSL, and not have the SSL connection terminate at the proxy. But to do this the traffic had to be redirected as the same name as the SSL certification. For example if your SSL certificate is for site.abc.com and that is the web address that resolves to your public IP, you must redirect the traffic as site.abc.com and not by the internal name of your server. Then your firewall must be able to resolve the SSL cert name (site.abc.com) to the address of your internal web server. To do so I edited the HOSTS file. Works great now.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top