websockets not allowed

[Marc66]

Hello
I have a problem with a client who has disabled webSockets, so no access to the Qlik Sense hub. He talks to me about a "Long polling" alternative.
Is there any alternative to access the hub without enabling webSockets?

[Miguel_Angel_Baeyens]

The access to the Hub itself or the QMC is mostly responded by the Repository API. However, the Engine API that opens and reloads apps, does require websockets.

What's the rationale of the client behind disabling a known and documented requirement for Qlik Sense? Is it a security concern, or hardware devices lacking support for the protocol, others?

[Marc66]

Hi,
to answer the question, it's an observability problem, the webSocket stream is blocked for this reason by the IT department.

[Daniele_Purrone]

I'm afraid there is no alternative: the technology relies on websocket.

[Marc66]

We will probably go for an exceptional exemption for some clients; security is more important than functionality. Thanks for your feedback.

[Daniele_Purrone]

I understand @Marc66. I would recommend suggesting an idea about replacing web socket with long polling,  detailing the reasons for that.

If that will happen, it won't for sure in the short period, but the product team is always interested in hearing the challenges our customers go through, in order to plan for the future.