Same issue. I am trying to figure this out as well. I have other web services and website that are working just fine, and I am hosting a sharepoint as well on standard http port 80. Nothing fancy, just to the point. I have tried disabling certain profile security features and even removed the profile security all together and same result.
As a test I created a simple DNAT rule on port 80 and only had to sign in once with a single prompt. Disabled the DNAT rule and went back to useing WAF and then the problem came back? It seems like it is having some sort of IIS authentication issue in IE?
This Issue is concerning NTLM authentication in IIS/Sharepoint. As per astaro Support it is actually a problem with NTLM an WAF. We will test Basic authentication with HTTPS and i will post my results
Thanks for the info, let me know what you come up with. I am stuck with the issue right now and I really don't want to switch over to SSL because of the constant invalid certificate errors that my end users will be dealing with.
I was able to use WAF with Sharepointservices 3.0 after disabling of NTLM ( interrogated windows authentication) in IIS and additional in Sharepoint. Only Basic Autentication is activ and it works. Disadvantage users need to authenticate in LAN to, but Remote Access through WAF goes only with one authentication. Important in WAF Virtaul Server must be HTTPS, while Basic Authentication insecure is.
Thanks for the update, only problem is this will not work for what I need. I prefer to use the Authentication based on active directory for my users. I would say that the concept of WAF is good, but not being able to handdle such a simple web service like sharepoint over standard http port 80 seems a little misleading in ease of use.
I hope something comes about for a fix on this sometime soon. I love the idea of not forwarding ports, but hate the constant work arounds to get something simple to work.
Ok, so I am working ok now using basic authintication, but I found that SharePoint Services will not work well with Cross site scripting enabled or HTML rewritting.
yes than's right. Cross site scripting is problem. And any exptions for Cross site scripting are without effect. It is a bug. The Hotfix must be availible soon.