kecoak
asked on
Integrated Windows Authentication?
http://msdn2.microsoft.com/en-us/library/ms955939.aspx#cs_gs_security_zhsy
-Integrated Windows authentication does not work over HTTP Proxy connections.
-Additional TCP ports have to be opened in the firewall.
I went to the above web site and checked that the integrated Windows Authentication does not work over HTTP Proxy connection? Why is that the case? IF I am not wrong, the proxy only there to forward the request? I mean it would be perfectly make sense to me to open additional port if required but I didn't get the idea that the IWA didn't work in the HTTP proxy connection.
any thought around this?
-Integrated Windows authentication does not work over HTTP Proxy connections.
-Additional TCP ports have to be opened in the firewall.
I went to the above web site and checked that the integrated Windows Authentication does not work over HTTP Proxy connection? Why is that the case? IF I am not wrong, the proxy only there to forward the request? I mean it would be perfectly make sense to me to open additional port if required but I didn't get the idea that the IWA didn't work in the HTTP proxy connection.
any thought around this?
ASKER
but if we were using NLTM, then shouldn't be no problem at all? As far as I am concerned Windows Authentication can be used either NTLM or Kerberos but even with Kerberos, this shouldn't be a problem at all.
Can you elaborate more about the "TRUST" how does it work?
Can you elaborate more about the "TRUST" how does it work?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
By "trust" it means the client can verify who the server is and the server can verify who the client is. When you throw a proxy in the middle of it, neither of them communicate directly to each other and therefore can't develop a trust..