This also happens vice versa. If you have transparent AD SSO in use, you cannot activate Webserver Protection Virtual Servers.
I assume this protection was implemented due a earlier bug I found that some features as transparent skiplists in the web proxy may kill transparent SSO.
But this is now definately a Bug, as Webserver Protecion and Web Proxy Profile with transparent SSO also gets blocked, if they are listening on two COMPLETELY DIFFERENT Interfaces (WAN vs. LAN)
So please fix this, and block only those configurations, where people try to activate transparent SSO AND a virtual webserver on the same interface - which may break things...
This also happens vice versa. If you have transparent AD SSO in use, you cannot activate Webserver Protection Virtual Servers.
I assume this protection was implemented due a earlier bug I found that some features as transparent skiplists in the web proxy may kill transparent SSO.
But this is now definately a Bug, as Webserver Protecion and Web Proxy Profile with transparent SSO also gets blocked, if they are listening on two COMPLETELY DIFFERENT Interfaces (WAN vs. LAN)
So please fix this, and block only those configurations, where people try to activate transparent SSO AND a virtual webserver on the same interface - which may break things...
I'm with Sascha on this, just keep the IP conflicts away -- I can't think of a scenario where I'd want transparent proxy listening on the outside network(s) and WAF on the inside network(s)... that's a major issue not being able to use one feature because another is enabled.
