V
vic
Hi,
I’ve got an ASP.NET 2.0 web application that requires SSL. In addition, the pages are configured to use Integrated Windows Authentication. I am having a problem getting automatic authentication to work for internal network users. If they try to access the page using an internal server name in the Url, the authentication takes place automatically but they must first deal with a warning page (in IE7) that alerts them to a problem with the site’s security certificate since the names don’t match up. However, if they access the page using the fully-qualified domain they get a dialog box asking them to authenticate. I thought if I added the fully-qualified secure domain name (https://mydomain.com) to the exception list (in IE7’s settings) for bypassing the proxy server the security credentials would carry through. But it’s not happening. How can I get integrated authentication to work while still using SSL?
Thanks for your help.
I’ve got an ASP.NET 2.0 web application that requires SSL. In addition, the pages are configured to use Integrated Windows Authentication. I am having a problem getting automatic authentication to work for internal network users. If they try to access the page using an internal server name in the Url, the authentication takes place automatically but they must first deal with a warning page (in IE7) that alerts them to a problem with the site’s security certificate since the names don’t match up. However, if they access the page using the fully-qualified domain they get a dialog box asking them to authenticate. I thought if I added the fully-qualified secure domain name (https://mydomain.com) to the exception list (in IE7’s settings) for bypassing the proxy server the security credentials would carry through. But it’s not happening. How can I get integrated authentication to work while still using SSL?
Thanks for your help.