IBM Security Verify

Hello!
We are using Qlik Sense through WebSeal and we ancountered an issue with timeouts.
Qlik Sense application can use multiple WebSocket connections on same page, some of then can be inactive if you don't use related parts of app.
The problem is - WebSeal closes such connections by timeout and this leads to error in Qlik Sense application.

For example:
You can set stanza timeout property to 10 minutes, then open Qlik Sense app, two WebSocket connections will be started:
First connection - for creating visualizations;
Second connection - for data load manager.
If you work 10 minutes in visualization editor, Qlik Sense will show error "Connection lost", because second WebSocket will be closed by WebSeal due to inactivity.

So, is it possible to use shared timeout for all WebSocket connections on same browser page or user session?

Qlik Sense, for example, has inactivity timeout too, but it applies to user session, not for separate connections in one session.



------------------------------
Александр Петухов
------------------------------

Original Message:
Sent: 9/6/2021 6:28:00 AM
From: Александр Петухов
Subject: [WebSeal] Share timeout between WebSockets on same page

Hello!
We are using Qlik Sense through WebSeal and we ancountered an issue with timeouts.
Qlik Sense application can use multiple WebSocket connections on same page, some of then can be inactive if you don't use related parts of app.
The problem is - WebSeal closes such connections by timeout and this leads to error in Qlik Sense application.

For example:
You can set stanza timeout property to 10 minutes, then open Qlik Sense app, two WebSocket connections will be started:
First connection - for creating visualizations;
Second connection - for data load manager.
If you work 10 minutes in visualization editor, Qlik Sense will show error "Connection lost", because second WebSocket will be closed by WebSeal due to inactivity.

So, is it possible to use shared timeout for all WebSocket connections on same browser page or user session?

Qlik Sense, for example, has inactivity timeout too, but it applies to user session, not for separate connections in one session.



------------------------------
Александр Петухов
------------------------------

Thanks for your answer!
I posted to Qlik community that this issue can not by resolved on WebSEAL side:
https://community.qlik.com/t5/Integration-Extension-APIs/Qlik-Sense-WebSocket-timeouts-in-IBM-WebSEAL-integration-via/td-p/1834478

------------------------------
Александр Петухов
------------------------------

Original Message:
Sent: Tue September 07, 2021 09:17 PM
From: Scott Exton
Subject: [WebSeal] Share timeout between WebSockets on same page

Unfortunately it is not currently possible to share Web Socket 'activity' across multiple sockets - even if the sockets are 'owned' by the same client.  The timeout for each Web Socket is treated individually.

 

Sorry that I don't have better news for you.

 

 

Scott A. Exton
Senior Software Engineer
Chief Programmer - IBM Security Verify Access
IBM Master Inventor

 

 

 

Original Message:
Sent: 9/6/2021 6:28:00 AM
From: Александр Петухов
Subject: [WebSeal] Share timeout between WebSockets on same page

Hello!
We are using Qlik Sense through WebSeal and we ancountered an issue with timeouts.
Qlik Sense application can use multiple WebSocket connections on same page, some of then can be inactive if you don't use related parts of app.
The problem is - WebSeal closes such connections by timeout and this leads to error in Qlik Sense application.

For example:
You can set stanza timeout property to 10 minutes, then open Qlik Sense app, two WebSocket connections will be started:
First connection - for creating visualizations;
Second connection - for data load manager.
If you work 10 minutes in visualization editor, Qlik Sense will show error "Connection lost", because second WebSocket will be closed by WebSeal due to inactivity.

So, is it possible to use shared timeout for all WebSocket connections on same browser page or user session?

Qlik Sense, for example, has inactivity timeout too, but it applies to user session, not for separate connections in one session.



------------------------------
Александр Петухов
------------------------------