SharePoint University

We have a 3rd party hosted, dedicated server running WSS 3.0. The primary SharePoint site was already set up and then an SSL certificate was added to the IIS site. I am trying to use alternate access mapping to force any request to http://www.somedomain.com over to https://www.somedomain.com. Basically, if someone comes to the http protocol I want them to go to https. I've set the mapping as Internal URL: https://www.somedomain.com; Zone: Default; Public URL for Zone: https://www.somedomain.com. This solves the problem that when someone enters http they are foced to https. It creates a new problem of forcing 2 logins. The sequence is:

1. Login to access http
2. Forwarded to https (as seen by alert dialog to that effect)
3. Login to access https
4. Access home page of site

If the person enters the https protocol first, then they only get one login as expected. Anyone have an idea how to fix this? There is very sensitive data on this site, so allowing any anonymous access to the site is right out.

FT

Doing this in a non-hosted mode would be a piece of cake. However, throwing hosting into the mix might be a bit tricky.

Just to see if I can give you or someone else an idea on how to fix your issue, I will describe how to do it normally.

-Use https:// only with SharePoint (meaning, have no AAM that uses the http version of your namespace)
-Create a new IIS virtual server with the host header of your site, listening on port 80
-Make the new virtual server redirect to https
-Use anonymous on the new IIS virtual server

Using these steps, you wouldn't get two prompts....but like I said, having hosting makes it a bit complicated.

Sorry I can't be of more help right now....