Hello,
In Windows Server 2012 R2 a new role called "Web Application Proxy" is included, which is the replacement of the "ADFS Proxy" which existed with ADFS 2.0.
However, some of our customers already have a reverse proxy implemented (Apache, Bluecoat, F5, TMG, ...). They ask us if they can use this Reverse Proxy to publish the ADFS 3.0 servers.
Their request seems logical because they could consolidate on a single reverse proxy, and they usually already have the HTTPS firewall flow opened to this reverse proxy.
While we know out of experience publishing ADFS works fine when the reverse proxy is SNI-compliant (and
there's also a fallback for non-SNI compliant devices), I would like to know if there's any other constraints that we need to be aware of when using other reverse proxies than the Microsoft Web Application Proxy?
Thanks!
Bart