This might be a bit OT so apologies in advance. Has anyone deployed WAP (Web Application Proxy) to replace an ISA or TMG installation? If so, how does this compare?
Currently we use ISA 2004 Enterprise with Windows NLB for publishing websites such as OWA with RSA authentication (which might change when we are fully 0365), but a majority of the websites published are just standard websites with authentication handled by the website vendors. (Such as access to the Pension, HR, Project management websites) and other hosted websites are pages required by our planning website, internet facing website (ourdomain.org) with no authentication. i.e publically accessible ones.
Most of my reading appears to suggest the uses for WAP are for publishing the likes of Lync, OWA, Sharepoint, RDS etc which require authentication rather than standard websites that are unauthenticated access. On ISA we have around 40 publishing/Listening rules
Wildcard SSL certificates. (*.ourdomain.org)
HTTP > HTTPS redirection rules.
Rules to redirect traffic from port 443 to custom ports i.e 50600 for DMZ based web servers.
Rule to allow HTTPS traffic to pass thru for servers that have their own SSL certificates installed directly.
Forwarding of Host Headers – for multiple sites that are hosted on one server but accessed via a single IP addressPublishing of OWAPublishing of OMA The two ISA servers have two NICs, one in one DMZ and one on another network
Just wondering from a real-world view how does WAP compare?