Qlik Sense Server access through a TMG

[#1]

Hi Qlik Community

We are setting up external network access to a Qlik Sense Server on the corporate network. All external connections are authenticated and routed through a Microsoft Forefront Threat Management Gateway, a firewall, and finally onto the Qlik Sense Server. This set-up is working fine for our Qlikview server, which we can access externally once authenticated by the TMG, but it seems to have trouble communicating with the Qlik Sense server.

After authenticating with the TMG we are receiving a page with Error code 64: Host not available. Tests on the TMG are currently giving us a HTTP 301 error - moved permanently, when attempting the connection.

Any guidance or tips would be greatly appreciated.

Many thanks

[korsikov]

if you foward to Qlik Sense server through a proxy, you must also traverse the web socket

[phaneendra_kunc]

I have the same problem. Were you able to resolve.

Kind of odd that we have qlikview TMG and it works without a problem. Not sure why Sense has a problem.

Any help is greatly appreciated.

[korsikov]

I ran into the same problem. If the user of the Internet everything works fine. and if users are in TMG problems begin

[Anonymous]

Same issue here!

We get stuck when QlikSense redirects us to Port 4244 for Windows Authentication.

It points us to the internal servername, instead of the external URL.

Not quite sure if there is a way to configure TMG to replace the servername in the response...

[korsikov]

You are wrong. Connect stuck after authentication. Tmg not allowed websocket on http. Try connect to you server use https.

[Anonymous]

HI!

For testing I have now turned the Virtual Proxy to "Allow Anonymous".

--> now I agree with you, we get an HTTP 500 Error on the first request to  "WSS://Servername"

--> websocket seems to be blocked.

Can you post your TMG configurations to allow websocket? It would help a lot!

Thx in advance

Roland

[korsikov]

sorry but i not use TMG in my environment. My clients faced with this problem.

He always use workaround - connect through https. TMG allow WS on https connection.

Also same problem with SQUID. Solved with add line in config "Allow CONNECT on 80 ports" add edit two timeouts

read_timeout, client_lifetime

[#9]

Hi Roland,

Did you ever get this working for TMG inbound?

Thanks,

Marc

[Anonymous]

hi!

no, we moved a proxy-node into the DMZ instead.

I think the problem was, that Qlik Sense Authentication does a port switch to 4244, which we never got working in TMG..