Hello,
We're wrestling with setting up Qlik Sense at a client who is using Azure AD Application Proxy to manage external access.
As far as the documentation indicates, there does not seem to be any special configuration required on the Azure side of things to enable websocket traffic, however we cannot see any websocket requests coming into their firewall (http request arrive and receive successful responses). We've got a support ticket open with Microsoft, but I wanted to check to see if anyone has successfully setup this type of scheme?
Thanks,
Mark
Relevant notes:
- Qlik article from Michael Robertshaw - indicates that Application Proxy supports websockets. ("Qlik Sense requires websocket connectivity that is supported by the Application Proxy since April 2018.")
- Microsoft blog by Alex Simons - indicates that Application Proxy connectors newer than version 1.5.612.0 support websockets & that no special configuration is required. ("The websocket application doesn't have any unique publishing requirements, and can be published the same way as all your other Application Proxy applications") Our customer is running connectors newer that the stated version.
- Microsoft article - details setup of Application Proxy but makes no mention of any websocket-specific configuration, further confirmation that no special setup is required?
- Customer is using a Palo Alto firewall; the firewall rules appear to be configured to allow websocket traffic & an inspection of the traffic logs do not show that any websocket traffic is being denied. (We don't see websocket traffic at all at the firewall.)
- Customer is using internal & external DNS to route both sets of users via the same FQDN, this appears to be working correctly.
