You are viewing limited content. For full access, please sign in.

Question

Question

Feature Request - Clear LF connection/session on Web client browser close

asked on March 31, 2023

Hi All,

 

We've hit a specific issue with a customer who uses an integration via the web client where they will open and close documents from another system via web URL's. 

 

They're continually seeing an issue, whereby the user runs out of active connections, as after opening and closing several documents, they recieve a 9030 error. You have to then manually go into the admin console and terminate their inactive sessions, which will then allow them to login to Laserfiche again.

 

I've noticed in testing, that this issue only occurs if the browser is closed between each document opening, if the browser is left open, you can seemingly open an unlimited number of tabs/documents. This is the current workaround to the issue.

 

I've also considered setting the idle timeout option within the repository to a very short time frame, however this may illegitimately terminate valid connections, with office documents open etc. So this isn't really a viable solution either.

 

I'd like to make a feature request to have the Laserfiche web client close the LF connection, when the browser is closed, to effectively 'tidy up' the active sessions in the same way the windows client does.

 

Is this possible? And if so what are the timescales when this might be implemented?

 

Cheers!

Chris Douglas

0 0

Answer

SELECTED ANSWER
replied on June 22, 2023

We're not planning any changes at this time.

0 0

Replies

replied on March 31, 2023

I understand the desire for a feature like this, but it's not really possible to implement in a reliable way. Especially with modern browsers adding more aggressive tab suspension behavior, there aren't reliable notifications from the browser that it is closing or a guarantee that the closing application can tell its server that it is closing. From the beginning, the standard way to close user sessions is by timing from the last time the server "saw" the user.

0 0
replied on April 1, 2023

Thanks Brian,

 

What about tackling this the other way around? If the user creates a connection to Laserfiche through the web client, if there is already a session there, it can use that connection rather than creating a new one?

 

Cheers!

Chris Douglas

0 0
replied on April 5, 2023

Honestly, I'd be pretty reluctant to open that can of worms. I see how it would help in your situation, but the hard cases seem really hard. In general it could easily appear to the user like the software is acting unpredictably. It's essentially replacing an easily understood timeout and reconnect mechanism with a much more complicated one, for which we need to try to determine which sessions represent the same physical user and of those which one they would want us to steal the connection from. And if it turned out that we took it from the wrong one, what is the user experience for that person?

0 0
replied on April 6, 2023

Hi Brian,

 

It should just pick-up any existing connection for the same application (web client) for logged on user, rather than creating a new user session. I wouldn't expect this to be the case for the other applications such as windows client, office integration, this would purely be for the web client, as the other applications handle the connection close correctly.

 

I'm asking as this is really causing headaches for one of our customers who has a Laserfiche integration with another system, and will open and close documents in quick succession. Multiple users are getting 'locked' out of Laserfiche daily which then need admin intervention to close some of the sessions.

 

What about making the concurrent connection limit higher? It's currently 5-7 or so concurrent connections per user account. What about upping this to say 50?

 

Cheers!

Chris Douglas

0 0
replied on June 13, 2023

Hi Brian,

 

Was there any clear direction on this agreed or discussed?

 

Cheers!

Chris Douglas

0 0
SELECTED ANSWER
replied on June 22, 2023

We're not planning any changes at this time.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.